From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] 9dae7a15aea76313c592c11db44e1386e85f86fe
Date: Sun, 4 Dec 2022 06:40:34 +0000 (UTC) [thread overview]
Message-ID: <20221204064034.CB2C360091@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 6004 bytes --]
_Testing issues_
Branch: tags/v22.11
9dae7a15aea76313c592c11db44e1386e85f86fe --> testing fail
Test environment and result as below:
+------------------------------------+--------------------+----------------------+----------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_unit_test |
+====================================+====================+======================+================+
| Windows Server 2019 | PASS | PASS | PASS |
+------------------------------------+--------------------+----------------------+----------------+
| FreeBSD 13 | PASS | SKIPPED | SKIPPED |
+------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 20.04 ARM Clang Native | PASS | SKIPPED | PASS |
+------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 20.04 ARM GCC Native | PASS | SKIPPED | PASS |
+------------------------------------+--------------------+----------------------+----------------+
| CentOS Stream 8 | PASS | SKIPPED | PASS |
+------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS | SKIPPED | SKIPPED |
+------------------------------------+--------------------+----------------------+----------------+
| Debian Buster | PASS | SKIPPED | PASS |
+------------------------------------+--------------------+----------------------+----------------+
| CentOS Stream 9 | PASS | SKIPPED | PASS |
+------------------------------------+--------------------+----------------------+----------------+
| RHEL 7 | PASS | SKIPPED | FAIL |
+------------------------------------+--------------------+----------------------+----------------+
| Debian Bullseye | PASS | SKIPPED | PASS |
+------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 22.04 | PASS | SKIPPED | PASS |
+------------------------------------+--------------------+----------------------+----------------+
| RHEL8 | PASS | SKIPPED | PASS |
+------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 20.04 ARM SVE | PASS | SKIPPED | SKIPPED |
+------------------------------------+--------------------+----------------------+----------------+
| Ubuntu 20.04 | SKIPPED | SKIPPED | PASS |
+------------------------------------+--------------------+----------------------+----------------+
| openSUSE Leap 15 | SKIPPED | SKIPPED | PASS |
+------------------------------------+--------------------+----------------------+----------------+
==== 20 line log output for RHEL 7 (dpdk_unit_test): ====
93/103 DPDK:fast-tests / telemetry_json_autotest OK 0.21 s
94/103 DPDK:fast-tests / telemetry_data_autotest OK 0.17 s
95/103 DPDK:fast-tests / table_autotest OK 12.68 s
96/103 DPDK:fast-tests / ring_pmd_autotest OK 0.18 s
97/103 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.32 s
98/103 DPDK:fast-tests / bitratestats_autotest OK 0.27 s
99/103 DPDK:fast-tests / latencystats_autotest OK 0.18 s
100/103 DPDK:fast-tests / pdump_autotest OK 5.36 s
101/103 DPDK:fast-tests / vdev_autotest OK 0.22 s
102/103 DPDK:fast-tests / compressdev_autotest SKIP 0.18 s
103/103 DPDK:fast-tests / telemetry_all SKIP 0.02 s
Ok: 93
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 9
Timeout: 0
Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK@4/dpdk/build/meson-logs/testlog.txt
==== End log output ====
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: clang 14.0.5-1.fc36
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/22519/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-12-04 6:40 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 6:40 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-16 5:38 dpdklab
2023-04-16 5:36 dpdklab
2023-04-15 10:29 dpdklab
2023-04-15 7:10 dpdklab
2023-04-14 6:02 dpdklab
2023-04-14 5:31 dpdklab
2023-04-13 5:35 dpdklab
2023-04-13 5:23 dpdklab
2023-04-12 5:35 dpdklab
2023-04-11 5:16 dpdklab
2023-04-10 4:48 dpdklab
2023-04-09 5:02 dpdklab
2023-04-08 5:09 dpdklab
2023-04-07 5:12 dpdklab
2023-04-06 12:10 dpdklab
2023-04-05 4:32 dpdklab
2023-04-05 4:23 dpdklab
2023-04-05 4:15 dpdklab
2023-04-04 4:46 dpdklab
2023-04-03 4:42 dpdklab
2023-04-02 4:50 dpdklab
2023-04-01 4:54 dpdklab
2023-03-31 18:52 dpdklab
2023-03-31 18:41 dpdklab
2023-03-29 4:45 dpdklab
2023-03-29 4:40 dpdklab
2023-03-29 4:31 dpdklab
2023-03-29 4:28 dpdklab
2023-03-16 5:02 dpdklab
2023-02-23 5:43 dpdklab
2023-02-23 5:34 dpdklab
2023-02-22 5:33 dpdklab
2023-02-19 5:44 dpdklab
2023-02-19 5:31 dpdklab
2023-02-19 5:28 dpdklab
2023-02-11 5:31 dpdklab
2023-02-11 5:31 dpdklab
2023-02-11 5:27 dpdklab
2023-02-10 5:34 dpdklab
2023-02-10 5:18 dpdklab
2023-01-22 5:23 dpdklab
2023-01-19 5:24 dpdklab
2023-01-13 5:43 dpdklab
2023-01-13 5:39 dpdklab
2023-01-13 5:24 dpdklab
2023-01-11 15:08 dpdklab
2023-01-11 5:41 dpdklab
2023-01-10 5:30 dpdklab
2023-01-10 5:27 dpdklab
2023-01-07 5:43 dpdklab
2023-01-07 5:27 dpdklab
2023-01-05 5:24 dpdklab
2023-01-02 5:23 dpdklab
2022-12-29 6:46 dpdklab
2022-12-29 6:46 dpdklab
2022-12-29 6:46 dpdklab
2022-12-29 6:45 dpdklab
2022-12-29 6:45 dpdklab
2022-12-29 6:45 dpdklab
2022-12-29 5:22 dpdklab
2022-12-28 5:42 dpdklab
2022-12-28 5:38 dpdklab
2022-12-26 7:02 dpdklab
2022-12-26 7:02 dpdklab
2022-12-26 7:02 dpdklab
2022-12-26 7:01 dpdklab
2022-12-21 9:56 dpdklab
2022-12-21 9:55 dpdklab
2022-12-21 9:55 dpdklab
2022-12-21 9:52 dpdklab
2022-12-21 9:52 dpdklab
2022-12-21 9:52 dpdklab
2022-12-21 9:52 dpdklab
2022-12-20 7:11 dpdklab
2022-12-20 7:10 dpdklab
2022-12-20 7:07 dpdklab
2022-12-20 7:07 dpdklab
2022-12-20 7:07 dpdklab
2022-12-20 7:07 dpdklab
2022-12-20 6:40 dpdklab
2022-12-04 6:44 dpdklab
2022-12-04 6:43 dpdklab
2022-12-04 6:34 dpdklab
2022-12-04 6:34 dpdklab
2022-12-04 6:33 dpdklab
2022-12-04 6:33 dpdklab
2022-12-04 6:32 dpdklab
2022-12-04 6:26 dpdklab
2022-12-04 5:30 dpdklab
2022-12-04 5:26 dpdklab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221204064034.CB2C360091@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).