From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Ali Alnubani <alialnu@nvidia.com>
Subject: |FAILURE| pw138575 [PATCH] buildtools: fix build with clang 17
Date: Wed, 20 Mar 2024 10:05:32 -0700 (PDT) [thread overview]
Message-ID: <65fb175c.d40a0220.110e5.a6fdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240320155814.617220-1-alialnu@nvidia.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/138575
_Testing issues_
Submitter: Ali Alnubani <alialnu@nvidia.com>
Date: Wednesday, March 20 2024 15:58:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138575 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian 11 (arm) | FAIL |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
==== 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.17s
104/112 DPDK:fast-tests / thash_autotest OK 0.18s
105/112 DPDK:fast-tests / threads_autotest OK 0.34s
106/112 DPDK:fast-tests / ticketlock_autotest OK 0.19s
107/112 DPDK:fast-tests / timer_autotest OK 2.49s
108/112 DPDK:fast-tests / trace_autotest OK 0.18s
109/112 DPDK:fast-tests / trace_autotest_with_traces OK 0.18s
110/112 DPDK:fast-tests / vdev_autotest OK 0.17s
111/112 DPDK:fast-tests / version_autotest OK 0.17s
112/112 DPDK:fast-tests / telemetry_all SKIP 0.01s 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 ====
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29604/
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-20 17:05 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240320155814.617220-1-alialnu@nvidia.com>
2024-03-20 15:37 ` |SUCCESS| " qemudev
2024-03-20 15:42 ` qemudev
2024-03-20 16:01 ` checkpatch
2024-03-20 16:47 ` dpdklab
2024-03-20 16:48 ` dpdklab
2024-03-20 16:48 ` dpdklab
2024-03-20 16:48 ` dpdklab
2024-03-20 16:48 ` dpdklab
2024-03-20 16:49 ` dpdklab
2024-03-20 16:49 ` dpdklab
2024-03-20 16:49 ` dpdklab
2024-03-20 16:49 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:51 ` dpdklab
2024-03-20 16:51 ` dpdklab
2024-03-20 16:51 ` dpdklab
2024-03-20 16:52 ` dpdklab
2024-03-20 16:52 ` dpdklab
2024-03-20 16:52 ` dpdklab
2024-03-20 16:52 ` dpdklab
2024-03-20 16:52 ` dpdklab
2024-03-20 16:53 ` dpdklab
2024-03-20 16:53 ` dpdklab
2024-03-20 16:53 ` dpdklab
2024-03-20 16:53 ` dpdklab
2024-03-20 16:54 ` dpdklab
2024-03-20 16:54 ` dpdklab
2024-03-20 16:57 ` dpdklab
2024-03-20 16:57 ` dpdklab
2024-03-20 16:58 ` dpdklab
2024-03-20 16:58 ` dpdklab
2024-03-20 16:58 ` dpdklab
2024-03-20 16:58 ` dpdklab
2024-03-20 16:58 ` dpdklab
2024-03-20 16:59 ` |FAILURE| " dpdklab
2024-03-20 16:59 ` |SUCCESS| " dpdklab
2024-03-20 16:59 ` |FAILURE| " dpdklab
2024-03-20 16:59 ` dpdklab
2024-03-20 16:59 ` |SUCCESS| " dpdklab
2024-03-20 16:59 ` dpdklab
2024-03-20 16:59 ` dpdklab
2024-03-20 17:01 ` dpdklab
2024-03-20 17:01 ` |FAILURE| " dpdklab
2024-03-20 17:01 ` |SUCCESS| " dpdklab
2024-03-20 17:01 ` |FAILURE| " dpdklab
2024-03-20 17:01 ` |SUCCESS| " dpdklab
2024-03-20 17:02 ` dpdklab
2024-03-20 17:02 ` dpdklab
2024-03-20 17:02 ` dpdklab
2024-03-20 17:02 ` dpdklab
2024-03-20 17:02 ` dpdklab
2024-03-20 17:03 ` |FAILURE| " dpdklab
2024-03-20 17:03 ` |SUCCESS| " dpdklab
2024-03-20 17:03 ` |FAILURE| " dpdklab
2024-03-20 17:03 ` |SUCCESS| " dpdklab
2024-03-20 17:03 ` |FAILURE| " dpdklab
2024-03-20 17:03 ` |SUCCESS| " dpdklab
2024-03-20 17:04 ` |FAILURE| " dpdklab
2024-03-20 17:04 ` dpdklab
2024-03-20 17:05 ` 0-day Robot
2024-03-20 17:05 ` |SUCCESS| " dpdklab
2024-03-20 17:05 ` dpdklab [this message]
2024-03-20 17:06 ` dpdklab
2024-03-20 17:06 ` dpdklab
2024-03-20 17:20 ` |FAILURE| " dpdklab
2024-03-20 17:21 ` |SUCCESS| " dpdklab
2024-03-20 17:25 ` |FAILURE| " dpdklab
2024-03-20 17:29 ` |SUCCESS| " dpdklab
2024-03-20 18:50 ` dpdklab
2024-03-21 11:37 ` dpdklab
2024-03-22 4:22 ` dpdklab
2024-03-22 5:02 ` 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=65fb175c.d40a0220.110e5.a6fdSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.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).