From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@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] 12c151767f1dee2a7636c457e522bfd6447996f7
Date: Wed, 13 Dec 2023 08:03:43 -0800 (PST) [thread overview]
Message-ID: <6579d5df.630a0220.e7a35.da14SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: 22.11-staging
12c151767f1dee2a7636c457e522bfd6447996f7 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Bullseye | FAIL |
+---------------------+----------------+
| CentOS Stream 8 | FAIL |
+---------------------+----------------+
| Fedora 38 | FAIL |
+---------------------+----------------+
| openSUSE Leap 15 | FAIL |
+---------------------+----------------+
| Fedora 37 | FAIL |
+---------------------+----------------+
==== 20 line log output for Fedora 37 (dpdk_unit_test): ====
95/105 DPDK:fast-tests / telemetry_json_autotest OK 0.17 s
96/105 DPDK:fast-tests / telemetry_data_autotest OK 0.17 s
97/105 DPDK:fast-tests / table_autotest OK 7.61 s
98/105 DPDK:fast-tests / ring_pmd_autotest OK 0.17 s
99/105 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.47 s
100/105 DPDK:fast-tests / bitratestats_autotest OK 0.17 s
101/105 DPDK:fast-tests / latencystats_autotest OK 0.17 s
102/105 DPDK:fast-tests / pdump_autotest OK 5.23 s
103/105 DPDK:fast-tests / vdev_autotest OK 0.17 s
104/105 DPDK:fast-tests / compressdev_autotest SKIP 0.17 s
105/105 DPDK:fast-tests / telemetry_all SKIP 0.01 s
Ok: 95
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/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)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27320/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-13 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 16:03 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-13 17:15 dpdklab
2023-12-13 16:53 dpdklab
2023-12-13 16:52 dpdklab
2023-12-13 16:52 dpdklab
2023-12-13 16:52 dpdklab
2023-12-13 16:49 dpdklab
2023-12-13 16:35 dpdklab
2023-12-13 15:57 dpdklab
2023-12-13 15:53 dpdklab
2023-12-13 15:52 dpdklab
2023-12-13 15:49 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=6579d5df.630a0220.e7a35.da14SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).