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| pw138785-138795 [PATCH] [v13,11/11] log: add optional supp
Date: Mon, 25 Mar 2024 19:33:31 -0700 (PDT) [thread overview]
Message-ID: <660233fb.170a0220.cd636.c159SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240326015827.825648-12-stephen@networkplumber.org>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/138795
_Testing issues_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, March 26 2024 01:57:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:0b82b5139fefe6eb5ec1a0b489fd193e8a99ab73
138785-138795 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | FAIL |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian 11 (arm) | FAIL |
+---------------------+----------------+
==== 20 line log output for Debian 11 (arm) (dpdk_unit_test): ====
102/112 DPDK:fast-tests / telemetry_data_autotest OK 0.18s
103/112 DPDK:fast-tests / telemetry_json_autotest OK 0.25s
104/112 DPDK:fast-tests / thash_autotest OK 0.20s
105/112 DPDK:fast-tests / threads_autotest OK 0.58s
106/112 DPDK:fast-tests / ticketlock_autotest OK 0.19s
107/112 DPDK:fast-tests / timer_autotest OK 2.68s
108/112 DPDK:fast-tests / trace_autotest OK 0.25s
109/112 DPDK:fast-tests / trace_autotest_with_traces OK 0.18s
110/112 DPDK:fast-tests / vdev_autotest OK 0.25s
111/112 DPDK:fast-tests / version_autotest OK 0.17s
112/112 DPDK:fast-tests / telemetry_all SKIP 0.08s 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
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29654/
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-26 2:33 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240326015827.825648-12-stephen@networkplumber.org>
2024-03-26 1:38 ` |SUCCESS| pw138785-138795 [PATCH v13 11/11] log: add optional support of syslog qemudev
2024-03-26 1:42 ` qemudev
2024-03-26 2:01 ` |WARNING| pw138795 " checkpatch
2024-03-26 2:31 ` |FAILURE| pw138785-138795 [PATCH] [v13,11/11] log: add optional supp dpdklab
2024-03-26 2:33 ` dpdklab [this message]
2024-03-26 2:33 ` |SUCCESS| " dpdklab
2024-03-26 2:34 ` dpdklab
2024-03-26 2:34 ` |FAILURE| " dpdklab
2024-03-26 2:34 ` |SUCCESS| " dpdklab
2024-03-26 2:35 ` |FAILURE| " dpdklab
2024-03-26 2:35 ` |SUCCESS| " dpdklab
2024-03-26 2:35 ` dpdklab
2024-03-26 2:36 ` |FAILURE| " dpdklab
2024-03-26 2:36 ` dpdklab
2024-03-26 2:36 ` |SUCCESS| " dpdklab
2024-03-26 2:36 ` dpdklab
2024-03-26 2:37 ` |FAILURE| " dpdklab
2024-03-26 2:37 ` |SUCCESS| " dpdklab
2024-03-26 2:37 ` dpdklab
2024-03-26 2:38 ` |FAILURE| " dpdklab
2024-03-26 2:38 ` dpdklab
2024-03-26 2:38 ` dpdklab
2024-03-26 2:38 ` |SUCCESS| " dpdklab
2024-03-26 2:38 ` dpdklab
2024-03-26 2:38 ` dpdklab
2024-03-26 2:39 ` |FAILURE| " dpdklab
2024-03-26 2:39 ` dpdklab
2024-03-26 2:39 ` |SUCCESS| " dpdklab
2024-03-26 2:39 ` |FAILURE| " dpdklab
2024-03-26 2:39 ` |SUCCESS| " dpdklab
2024-03-26 2:39 ` dpdklab
2024-03-26 2:39 ` dpdklab
2024-03-26 2:39 ` dpdklab
2024-03-26 2:40 ` dpdklab
2024-03-26 2:40 ` dpdklab
2024-03-26 2:40 ` dpdklab
2024-03-26 2:40 ` |FAILURE| " dpdklab
2024-03-26 2:42 ` |SUCCESS| " dpdklab
2024-03-26 2:43 ` dpdklab
2024-03-26 2:44 ` |FAILURE| " dpdklab
2024-03-26 2:45 ` |SUCCESS| " dpdklab
2024-03-26 2:45 ` |FAILURE| " dpdklab
2024-03-26 2:45 ` |SUCCESS| " dpdklab
2024-03-26 2:45 ` dpdklab
2024-03-26 2:45 ` |FAILURE| " dpdklab
2024-03-26 2:46 ` |SUCCESS| " dpdklab
2024-03-26 2:47 ` |FAILURE| " dpdklab
2024-03-26 2:47 ` |SUCCESS| " dpdklab
2024-03-26 2:48 ` dpdklab
2024-03-26 2:48 ` |FAILURE| " dpdklab
2024-03-26 2:48 ` |SUCCESS| " dpdklab
2024-03-26 2:49 ` |FAILURE| " dpdklab
2024-03-26 2:49 ` |SUCCESS| " dpdklab
2024-03-26 2:50 ` dpdklab
2024-03-26 2:50 ` dpdklab
2024-03-26 2:50 ` |FAILURE| " dpdklab
2024-03-26 2:50 ` dpdklab
2024-03-26 2:51 ` |SUCCESS| " dpdklab
2024-03-26 2:51 ` dpdklab
2024-03-26 2:51 ` |FAILURE| " dpdklab
2024-03-26 2:51 ` dpdklab
2024-03-26 2:51 ` dpdklab
2024-03-26 2:52 ` dpdklab
2024-03-26 2:53 ` dpdklab
2024-03-26 2:53 ` dpdklab
2024-03-26 2:53 ` |SUCCESS| " dpdklab
2024-03-26 2:54 ` dpdklab
2024-03-26 2:55 ` |FAILURE| " dpdklab
2024-03-26 2:55 ` |SUCCESS| " dpdklab
2024-03-26 3:00 ` dpdklab
2024-03-26 3:00 ` dpdklab
2024-03-26 3:04 ` |SUCCESS| pw138795 [PATCH v13 11/11] log: add optional support of syslog 0-day Robot
2024-03-26 3:06 ` |FAILURE| pw138785-138795 [PATCH] [v13,11/11] log: add optional supp dpdklab
2024-03-26 3:12 ` |SUCCESS| " dpdklab
2024-03-26 3:35 ` dpdklab
2024-03-26 3:56 ` dpdklab
2024-04-01 19:16 ` dpdklab
2024-04-01 19:20 ` dpdklab
2024-04-01 19:39 ` dpdklab
2024-04-01 19:43 ` dpdklab
2024-04-01 19:47 ` 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=660233fb.170a0220.cd636.c159SMTPIN_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).