automatic DPDK test reports
 help / color / mirror / Atom feed
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| pw155228-155240 [PATCH] [v4,13/13] pdump: mark API and app
Date: Tue, 15 Jul 2025 10:10:48 -0700 (PDT)	[thread overview]
Message-ID: <68768b98.050a0220.3346e3.a3bdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250715161700.103209-14-stephen@networkplumber.org>

Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/155240

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, July 15 2025 16:15:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:9fe9c0b231c8da5435bfccb1963121b4277f961c

155228-155240 --> testing issues

Upstream job id: Generic-VM-Unit-Test-DPDK#29958

Test environment and result as below:

+-------------------------------+----------------+
|          Environment          | dpdk_unit_test |
+===============================+================+
| Windows Server 2022           | FAIL           |
+-------------------------------+----------------+
| CentOS Stream 9               | PEND           |
+-------------------------------+----------------+
| CentOS Stream 10              | PEND           |
+-------------------------------+----------------+
| Fedora Linux 40               | PEND           |
+-------------------------------+----------------+
| Debian GNU/Linux 12           | PEND           |
+-------------------------------+----------------+
| Fedora Linux 41               | PEND           |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 8.10 | PEND           |
+-------------------------------+----------------+
| Ubuntu 20.04                  | PEND           |
+-------------------------------+----------------+
| Red Hat Enterprise Linux 9.5  | PEND           |
+-------------------------------+----------------+
| Ubuntu 24.04                  | PEND           |
+-------------------------------+----------------+
| Ubuntu 22.04                  | PEND           |
+-------------------------------+----------------+

==== Unit test summary for Windows Server 2022 (dpdk_unit_test): ====
Failed to get the unit test results.
Displaying the unit test results is not supported for some environments,
such as our aarch32 testing, where meson is not used to run the tests.
Download the logs available on our CI site.
==== End log output ====

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521

CentOS Stream 9
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-7)

CentOS Stream 10
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-8)

Fedora Linux 40
	Kernel: 5.15
	Compiler: clang gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)

Debian GNU/Linux 12
	Kernel: 5.15
	Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0

Fedora Linux 41
	Kernel: 5.15
	Compiler: clang gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)

Red Hat Enterprise Linux 8.10
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-22)

Ubuntu 20.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Red Hat Enterprise Linux 9.5
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)

Ubuntu 24.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

Ubuntu 22.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33660/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2025-07-15 17:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250715161700.103209-14-stephen@networkplumber.org>
2025-07-15 15:45 ` |SUCCESS| pw155228-155240 [PATCH v4 13/13] pdump: mark API and application as deprecated qemudev
2025-07-15 15:50 ` |FAILURE| " qemudev
2025-07-15 16:17 ` |SUCCESS| pw155240 " checkpatch
2025-07-15 17:04 ` |FAILURE| " 0-day Robot
2025-07-15 17:08 ` |SUCCESS| pw155228-155240 [PATCH] [v4,13/13] pdump: mark API and app dpdklab
2025-07-15 17:10 ` dpdklab [this message]
2025-07-15 17:12 ` |PENDING| " dpdklab
2025-07-15 17:15 ` |SUCCESS| " dpdklab
2025-07-15 17:17 ` |FAILURE| " dpdklab
2025-07-15 17:22 ` |SUCCESS| " dpdklab
2025-07-15 17:25 ` dpdklab
2025-07-15 17:25 ` dpdklab
2025-07-15 17:26 ` |FAILURE| " dpdklab
2025-07-15 17:28 ` dpdklab
2025-07-15 17:30 ` |SUCCESS| " dpdklab
2025-07-15 17:39 ` |FAILURE| " dpdklab
2025-07-15 17:45 ` dpdklab
2025-07-15 17:49 ` |SUCCESS| " dpdklab
2025-07-15 17:50 ` |FAILURE| " dpdklab
2025-07-15 17:56 ` dpdklab
2025-07-15 17:59 ` dpdklab
2025-07-15 18:03 ` dpdklab
2025-07-15 18:07 ` dpdklab
2025-07-15 18:12 ` dpdklab
2025-07-15 18:12 ` dpdklab
2025-07-15 18:13 ` dpdklab
2025-07-15 18:15 ` dpdklab
2025-07-15 18:18 ` dpdklab
2025-07-15 18:22 ` dpdklab
2025-07-15 18:37 ` |SUCCESS| " dpdklab
2025-07-15 18:47 ` |FAILURE| " dpdklab
2025-07-15 19:27 ` dpdklab
2025-07-15 20:47 ` |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=68768b98.050a0220.3346e3.a3bdSMTPIN_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).