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| pw155643-155655 [PATCH] [v8,13/13] app/dumpcap: use port m
Date: Mon, 04 Aug 2025 10:29:31 -0700 (PDT) [thread overview]
Message-ID: <6890edfb.c80a0220.583d2.93f8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250804163039.138959-14-stephen@networkplumber.org>
Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/155655
_Testing issues_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Monday, August 04 2025 16:27:44
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:38543d33bd47fc0ee21f59db80a8763620741879
155643-155655 --> testing issues
Upstream job id: Generic-DPDK-Compile-Meson#414701
Test environment and result as below:
+------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==============================+====================+
| Ubuntu 20.04 | PEND |
+------------------------------+--------------------+
| Debian GNU/Linux 12 | PEND |
+------------------------------+--------------------+
| Red Hat Enterprise Linux 9.5 | PEND |
+------------------------------+--------------------+
| Fedora Linux 40 | PEND |
+------------------------------+--------------------+
| Fedora Linux 41 | PEND |
+------------------------------+--------------------+
Ubuntu 20.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Debian GNU/Linux 12
Kernel: 5.4
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Red Hat Enterprise Linux 9.5
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
Fedora Linux 40
Kernel: 5.4
Compiler: clang gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora Linux 41
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33808/
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:[~2025-08-04 17:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250804163039.138959-14-stephen@networkplumber.org>
2025-08-04 15:57 ` |SUCCESS| pw155643-155655 [PATCH v8 13/13] app/dumpcap: use port mirror instead of pdump qemudev
2025-08-04 16:02 ` qemudev
2025-08-04 16:31 ` |SUCCESS| pw155655 " checkpatch
2025-08-04 17:14 ` |SUCCESS| pw155643-155655 [PATCH] [v8,13/13] app/dumpcap: use port m dpdklab
2025-08-04 17:16 ` |PENDING| " dpdklab
2025-08-04 17:20 ` |SUCCESS| " dpdklab
2025-08-04 17:29 ` dpdklab
2025-08-04 17:29 ` dpdklab [this message]
2025-08-04 17:29 ` |FAILURE| " dpdklab
2025-08-04 17:29 ` dpdklab
2025-08-04 17:31 ` dpdklab
2025-08-04 17:31 ` |SUCCESS| " dpdklab
2025-08-04 17:44 ` |FAILURE| pw155655 [PATCH v8 13/13] app/dumpcap: use port mirror instead of pdump 0-day Robot
2025-08-04 17:46 ` |FAILURE| pw155643-155655 [PATCH] [v8,13/13] app/dumpcap: use port m dpdklab
2025-08-04 17:51 ` dpdklab
2025-08-04 17:52 ` dpdklab
2025-08-04 17:52 ` |SUCCESS| " dpdklab
2025-08-04 17:59 ` dpdklab
2025-08-04 18:13 ` dpdklab
2025-08-04 18:23 ` |FAILURE| " dpdklab
2025-08-04 18:26 ` |SUCCESS| " 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=6890edfb.c80a0220.583d2.93f8SMTPIN_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).