From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |FAILURE| [GIT MASTER] 6ef07151aac4b4d9601d547f94a996d1c71b3871
Date: Sun, 07 Jan 2024 18:19:14 -0800 (PST) [thread overview]
Message-ID: <659b5ba2.4a0a0220.acd5f.de18SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: dpdk
6ef07151aac4b4d9601d547f94a996d1c71b3871 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | FAIL |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
==== 20 line log output for Debian Buster (dpdk_unit_test): ====
100/110 DPDK:fast-tests / telemetry_data_autotest OK 0.22 s
101/110 DPDK:fast-tests / telemetry_json_autotest OK 0.22 s
102/110 DPDK:fast-tests / thash_autotest OK 0.22 s
103/110 DPDK:fast-tests / threads_autotest OK 0.37 s
104/110 DPDK:fast-tests / ticketlock_autotest OK 0.22 s
105/110 DPDK:fast-tests / timer_autotest OK 2.52 s
106/110 DPDK:fast-tests / trace_autotest OK 0.22 s
107/110 DPDK:fast-tests / trace_autotest_with_traces OK 0.22 s
108/110 DPDK:fast-tests / vdev_autotest OK 0.22 s
109/110 DPDK:fast-tests / version_autotest OK 0.22 s
110/110 DPDK:fast-tests / telemetry_all SKIP 0.01 s
Ok: 99
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 10
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 ====
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27598/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-08 2:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 2:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-08 2:30 dpdklab
2024-01-08 2:22 dpdklab
2024-01-08 2:21 dpdklab
2024-01-08 2:19 dpdklab
2024-01-08 2:17 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=659b5ba2.4a0a0220.acd5f.de18SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
/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).