From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Bruce Richardson <bruce.richardson@intel.com>
Subject: |FAILURE| pw132285 [PATCH] eventdev: drop custom OS defines
Date: Tue, 03 Oct 2023 11:23:01 -0700 (PDT) [thread overview]
Message-ID: <651c5c05.810a0220.e5aba.7eabSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/132285
_Testing issues_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tuesday, October 03 2023 17:01:15
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: master
CommitID:9b1122634e8affeb1a3d957f3a96e48ae17956bc
132285 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | FAIL |
+---------------------+----------------+
| Fedora 38 | FAIL |
+---------------------+----------------+
| Debian Buster | FAIL |
+---------------------+----------------+
| CentOS Stream 9 | FAIL |
+---------------------+----------------+
| Fedora 37 | FAIL |
+---------------------+----------------+
==== 20 line log output for Fedora 37 (dpdk_unit_test): ====
98/108 DPDK:fast-tests / telemetry_data_autotest OK 0.27 s
99/108 DPDK:fast-tests / telemetry_json_autotest OK 0.35 s
100/108 DPDK:fast-tests / thash_autotest OK 0.18 s
101/108 DPDK:fast-tests / threads_autotest OK 0.45 s
102/108 DPDK:fast-tests / ticketlock_autotest OK 0.23 s
103/108 DPDK:fast-tests / timer_autotest OK 3.01 s
104/108 DPDK:fast-tests / trace_autotest OK 0.27 s
105/108 DPDK:fast-tests / trace_autotest_with_traces OK 0.37 s
106/108 DPDK:fast-tests / vdev_autotest OK 0.19 s
107/108 DPDK:fast-tests / version_autotest OK 0.27 s
108/108 DPDK:fast-tests / telemetry_all SKIP 0.06 s
Ok: 96
Expected Fail: 0
Fail: 3
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)
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
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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/27815/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-03 18:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 18:23 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-03 18:51 dpdklab
2023-10-03 18:49 dpdklab
2023-10-03 18:45 dpdklab
2023-10-03 18:41 dpdklab
2023-10-03 18:39 dpdklab
2023-10-03 18:24 dpdklab
2023-10-03 18:15 dpdklab
2023-10-03 18:12 dpdklab
2023-10-03 18:08 dpdklab
2023-10-03 17:56 dpdklab
[not found] <20231003170115.571133-1-bruce.richardson@intel.com>
2023-10-03 16:46 ` qemudev
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=651c5c05.810a0220.e5aba.7eabSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bruce.richardson@intel.com \
--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).