From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Sinan Kaya <okaya@kernel.org>
Subject: |FAILURE| pw130353-130360 [PATCH] [v4,8/8] eal: initialize worker th
Date: Tue, 15 Aug 2023 09:26:55 -0700 (PDT) [thread overview]
Message-ID: <64dba74f.050a0220.6c160.c0afSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/130360
_Testing issues_
Submitter: Sinan Kaya <okaya@kernel.org>
Date: Tuesday, August 15 2023 14:50:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:68150b90bda5e8f81ad1b1bad82be653b1d42a81
130353-130360 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | FAIL |
+---------------------+----------------+
| Fedora 37 | FAIL |
+---------------------+----------------+
| CentOS Stream 8 | FAIL |
+---------------------+----------------+
| Debian Buster | FAIL |
+---------------------+----------------+
| CentOS Stream 9 | FAIL |
+---------------------+----------------+
==== 20 line log output for CentOS Stream 9 (dpdk_unit_test): ====
96/106 DPDK:fast-tests / table_autotest OK 5.98 s
97/106 DPDK:fast-tests / ring_pmd_autotest OK 0.17 s
98/106 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.47 s
99/106 DPDK:fast-tests / bitratestats_autotest OK 0.17 s
100/106 DPDK:fast-tests / latencystats_autotest OK 0.17 s
101/106 DPDK:fast-tests / pdump_autotest OK 5.23 s
102/106 DPDK:fast-tests / vdev_autotest OK 0.17 s
103/106 DPDK:fast-tests / rawdev_autotest OK 0.17 s
104/106 DPDK:fast-tests / pdcp_autotest SKIP 0.17 s
105/106 DPDK:fast-tests / compressdev_autotest SKIP 0.17 s
106/106 DPDK:fast-tests / telemetry_all SKIP 0.01 s
Ok: 96
Expected Fail: 0
Fail: 1
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)
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27344/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-15 16:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 16:26 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-15 16:52 dpdklab
2023-08-15 16:51 dpdklab
2023-08-15 16:43 dpdklab
2023-08-15 16:43 dpdklab
2023-08-15 16:40 dpdklab
2023-08-15 16:39 dpdklab
2023-08-15 16:35 dpdklab
2023-08-15 16:33 dpdklab
2023-08-15 16:32 dpdklab
2023-08-15 16:31 dpdklab
2023-08-15 16:30 dpdklab
2023-08-15 16:29 dpdklab
2023-08-15 16:27 dpdklab
2023-08-15 16:26 dpdklab
2023-08-15 16:26 dpdklab
2023-08-15 16:25 dpdklab
2023-08-15 16:24 dpdklab
2023-08-15 16:23 dpdklab
2023-08-15 16:23 dpdklab
2023-08-15 16:22 dpdklab
2023-08-15 16:22 dpdklab
2023-08-15 16:21 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=64dba74f.050a0220.6c160.c0afSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=okaya@kernel.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).