From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Rahul Gupta <rahulgupt@linux.microsoft.com>
Subject: |FAILURE| pw135872 [PATCH] eal: refactor rte_eal_init into sub-funct
Date: Mon, 15 Jan 2024 02:59:52 -0800 (PST) [thread overview]
Message-ID: <65a51028.920a0220.df0da.b18aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/135872
_Testing issues_
Submitter: Rahul Gupta <rahulgupt@linux.microsoft.com>
Date: Monday, January 15 2024 08:50:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d4af9a82063e4c39568191eaa12955d3ca39581a
135872 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | FAIL |
+---------------------+----------------+
| CentOS Stream 8 | FAIL |
+---------------------+----------------+
| Debian Bullseye | FAIL |
+---------------------+----------------+
| CentOS Stream 9 | FAIL |
+---------------------+----------------+
==== 20 line log output for CentOS Stream 9 (dpdk_unit_test): ====
100/110 DPDK:fast-tests / telemetry_data_autotest OK 0.22 s
101/110 DPDK:fast-tests / telemetry_json_autotest OK 0.22 s
102/110 DPDK:fast-tests / thash_autotest OK 0.22 s
103/110 DPDK:fast-tests / threads_autotest OK 0.37 s
104/110 DPDK:fast-tests / ticketlock_autotest OK 0.22 s
105/110 DPDK:fast-tests / timer_autotest OK 1.52 s
106/110 DPDK:fast-tests / trace_autotest OK 0.22 s
107/110 DPDK:fast-tests / trace_autotest_with_traces OK 0.22 s
108/110 DPDK:fast-tests / vdev_autotest OK 0.22 s
109/110 DPDK:fast-tests / version_autotest OK 0.22 s
110/110 DPDK:fast-tests / telemetry_all SKIP 0.01 s
Ok: 98
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 10
Timeout: 1
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)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-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/28863/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-15 10:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 10:59 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-15 12:08 dpdklab
2024-01-15 12:05 dpdklab
2024-01-15 11:44 dpdklab
2024-01-15 11:33 dpdklab
2024-01-15 11:31 dpdklab
2024-01-15 11:24 dpdklab
2024-01-15 11:24 dpdklab
2024-01-15 11:21 dpdklab
2024-01-15 11:19 dpdklab
2024-01-15 11:10 dpdklab
2024-01-15 11:10 dpdklab
2024-01-15 11:05 dpdklab
2024-01-15 10:56 dpdklab
2024-01-15 10:55 dpdklab
2024-01-15 10:51 dpdklab
2024-01-15 10:49 dpdklab
2024-01-15 10:46 dpdklab
2024-01-15 10:40 dpdklab
2024-01-15 10:39 dpdklab
2024-01-15 10:38 dpdklab
2024-01-15 10:37 dpdklab
2024-01-15 10:36 dpdklab
2024-01-15 10:35 dpdklab
2024-01-15 10:34 dpdklab
2024-01-15 10:34 dpdklab
2024-01-15 10:32 dpdklab
2024-01-15 10:20 dpdklab
2024-01-15 10:18 dpdklab
2024-01-15 10:18 dpdklab
2024-01-15 10:17 dpdklab
2024-01-15 10:16 dpdklab
2024-01-15 10:15 dpdklab
2024-01-15 10:01 dpdklab
2024-01-15 10:00 dpdklab
2024-01-15 10:00 dpdklab
2024-01-15 10:00 dpdklab
2024-01-15 9:59 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=65a51028.920a0220.df0da.b18aSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=rahulgupt@linux.microsoft.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).