From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Stephen Hemminger <stephen@networkplumber.org>
Subject: |FAILURE| pw138771-138784 [PATCH] [v12,14/14] maintainers: add for l
Date: Mon, 25 Mar 2024 14:49:01 -0700 (PDT) [thread overview]
Message-ID: <6601f14d.050a0220.ff48f.8cb5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240325205405.669897-15-stephen@networkplumber.org>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/138784
_Testing issues_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Monday, March 25 2024 20:47:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:0b82b5139fefe6eb5ec1a0b489fd193e8a99ab73
138771-138784 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | FAIL |
+---------------------+----------------+
| CentOS Stream 9 | FAIL |
+---------------------+----------------+
| CentOS Stream 8 | FAIL |
+---------------------+----------------+
| Windows Server 2022 | FAIL |
+---------------------+----------------+
| Debian Bullseye | FAIL |
+---------------------+----------------+
| Debian 11 (arm) | FAIL |
+---------------------+----------------+
| Fedora 37 | FAIL |
+---------------------+----------------+
==== 20 line log output for Fedora 37 (dpdk_unit_test): ====
101/111 DPDK:fast-tests / telemetry_data_autotest OK 0.22 s
102/111 DPDK:fast-tests / telemetry_json_autotest OK 0.22 s
103/111 DPDK:fast-tests / thash_autotest OK 0.22 s
104/111 DPDK:fast-tests / threads_autotest OK 0.37 s
105/111 DPDK:fast-tests / ticketlock_autotest OK 0.22 s
106/111 DPDK:fast-tests / timer_autotest OK 2.52 s
107/111 DPDK:fast-tests / trace_autotest OK 0.22 s
108/111 DPDK:fast-tests / trace_autotest_with_traces OK 0.22 s
109/111 DPDK:fast-tests / vdev_autotest OK 0.22 s
110/111 DPDK:fast-tests / version_autotest OK 0.22 s
111/111 DPDK:fast-tests / telemetry_all SKIP 0.01 s
Ok: 100
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 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29653/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-25 21:49 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240325205405.669897-15-stephen@networkplumber.org>
2024-03-25 20:34 ` |SUCCESS| pw138771-138784 [PATCH v12 14/14] maintainers: add for log library qemudev
2024-03-25 20:38 ` |FAILURE| " qemudev
2024-03-25 20:56 ` |SUCCESS| pw138784 " checkpatch
2024-03-25 21:37 ` |FAILURE| pw138771-138784 [PATCH] [v12,14/14] maintainers: add for l dpdklab
2024-03-25 21:37 ` dpdklab
2024-03-25 21:37 ` dpdklab
2024-03-25 21:37 ` dpdklab
2024-03-25 21:38 ` |SUCCESS| " dpdklab
2024-03-25 21:38 ` dpdklab
2024-03-25 21:38 ` |FAILURE| " dpdklab
2024-03-25 21:38 ` dpdklab
2024-03-25 21:38 ` dpdklab
2024-03-25 21:38 ` dpdklab
2024-03-25 21:39 ` dpdklab
2024-03-25 21:39 ` dpdklab
2024-03-25 21:39 ` |SUCCESS| " dpdklab
2024-03-25 21:39 ` |FAILURE| " dpdklab
2024-03-25 21:39 ` dpdklab
2024-03-25 21:39 ` dpdklab
2024-03-25 21:40 ` |SUCCESS| " dpdklab
2024-03-25 21:40 ` |FAILURE| " dpdklab
2024-03-25 21:40 ` dpdklab
2024-03-25 21:40 ` dpdklab
2024-03-25 21:40 ` |SUCCESS| " dpdklab
2024-03-25 21:40 ` |FAILURE| " dpdklab
2024-03-25 21:41 ` dpdklab
2024-03-25 21:41 ` dpdklab
2024-03-25 21:41 ` |SUCCESS| " dpdklab
2024-03-25 21:41 ` |FAILURE| " dpdklab
2024-03-25 21:41 ` dpdklab
2024-03-25 21:41 ` dpdklab
2024-03-25 21:42 ` dpdklab
2024-03-25 21:42 ` dpdklab
2024-03-25 21:42 ` dpdklab
2024-03-25 21:42 ` |SUCCESS| " dpdklab
2024-03-25 21:42 ` |WARNING| " dpdklab
2024-03-25 21:42 ` |FAILURE| " dpdklab
2024-03-25 21:43 ` |SUCCESS| " dpdklab
2024-03-25 21:43 ` |FAILURE| " dpdklab
2024-03-25 21:43 ` dpdklab
2024-03-25 21:43 ` dpdklab
2024-03-25 21:43 ` dpdklab
2024-03-25 21:44 ` dpdklab
2024-03-25 21:44 ` dpdklab
2024-03-25 21:44 ` dpdklab
2024-03-25 21:44 ` |FAILURE| pw138784 [PATCH v12 14/14] maintainers: add for log library 0-day Robot
2024-03-25 21:44 ` |FAILURE| pw138771-138784 [PATCH] [v12,14/14] maintainers: add for l dpdklab
2024-03-25 21:44 ` dpdklab
2024-03-25 21:44 ` |SUCCESS| " dpdklab
2024-03-25 21:45 ` |FAILURE| " dpdklab
2024-03-25 21:45 ` dpdklab
2024-03-25 21:46 ` |SUCCESS| " dpdklab
2024-03-25 21:46 ` |FAILURE| " dpdklab
2024-03-25 21:46 ` |SUCCESS| " dpdklab
2024-03-25 21:47 ` dpdklab
2024-03-25 21:47 ` |FAILURE| " dpdklab
2024-03-25 21:47 ` |SUCCESS| " dpdklab
2024-03-25 21:47 ` |FAILURE| " dpdklab
2024-03-25 21:48 ` dpdklab
2024-03-25 21:48 ` dpdklab
2024-03-25 21:49 ` dpdklab [this message]
2024-03-25 21:49 ` dpdklab
2024-03-25 21:50 ` |SUCCESS| " dpdklab
2024-03-25 21:50 ` dpdklab
2024-03-25 21:51 ` dpdklab
2024-03-25 21:51 ` |FAILURE| " dpdklab
2024-03-25 21:51 ` dpdklab
2024-03-25 21:52 ` dpdklab
2024-03-25 21:53 ` |SUCCESS| " dpdklab
2024-03-25 21:54 ` dpdklab
2024-03-25 21:55 ` |FAILURE| " dpdklab
2024-03-25 22:01 ` dpdklab
2024-03-25 22:07 ` dpdklab
2024-03-25 22:52 ` dpdklab
2024-03-25 23:16 ` |SUCCESS| " dpdklab
2024-03-25 23:56 ` dpdklab
2024-04-01 17:52 ` dpdklab
2024-04-01 17:53 ` dpdklab
2024-04-01 18:10 ` dpdklab
2024-04-01 18:29 ` dpdklab
2024-04-01 18:33 ` 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=6601f14d.050a0220.ff48f.8cb5SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=stephen@networkplumber.org \
--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).