From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |FAILURE| [GIT MASTER] 0d7f7a7171484a12f6059f71a2e1a82c5bfaaa89
Date: Sat, 23 Mar 2024 00:06:59 -0700 (PDT) [thread overview]
Message-ID: <65fe7f93.0d0a0220.6add.5315SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: dpdk-next-net
0d7f7a7171484a12f6059f71a2e1a82c5bfaaa89 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Debian 11 (arm) | FAIL |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
==== 20 line log output for Debian 11 (arm) (dpdk_unit_test): ====
102/112 DPDK:fast-tests / telemetry_data_autotest OK 0.17s
103/112 DPDK:fast-tests / telemetry_json_autotest OK 0.17s
104/112 DPDK:fast-tests / thash_autotest OK 0.17s
105/112 DPDK:fast-tests / threads_autotest OK 0.33s
106/112 DPDK:fast-tests / ticketlock_autotest OK 0.18s
107/112 DPDK:fast-tests / timer_autotest OK 2.50s
108/112 DPDK:fast-tests / trace_autotest OK 0.18s
109/112 DPDK:fast-tests / trace_autotest_with_traces OK 0.18s
110/112 DPDK:fast-tests / vdev_autotest OK 0.17s
111/112 DPDK:fast-tests / version_autotest OK 0.17s
112/112 DPDK:fast-tests / telemetry_all SKIP 0.01s exit status 77
Ok: 101
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 ====
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28610/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-03-23 7:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 7:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-23 7:16 dpdklab
2024-03-23 7:16 dpdklab
2024-03-23 7:09 dpdklab
2024-03-23 7:08 dpdklab
2024-03-23 7:04 dpdklab
2024-03-23 7:01 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=65fe7f93.0d0a0220.6add.5315SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.com \
--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).