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
Subject: |SUCCESS| pw153590 [PATCH] [v3] ethdev: fix the bug where the flag v
Date: Thu, 22 May 2025 12:38:15 -0700 (PDT)	[thread overview]
Message-ID: <682f7d27.050a0220.197c1c.1bbdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250522074242.30376-1-sunyang.wu@jaguarmicro.com>

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/153590

_Testing PASS_

Submitter: Sunyang Wu <sunyang.wu@jaguarmicro.com>
Date: Thursday, May 22 2025 07:42:42 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a0ad790eb9fcef4b00366ae474132bee4bcdab75

153590 --> testing pass

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

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 10    | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Fedora 41           | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Fedora 41 (Clang)   | PASS           |
+---------------------+----------------+
| Fedora 40 (Clang)   | PASS           |
+---------------------+----------------+
| RHEL9               | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| Fedora 40           | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+
| Ubuntu 24.04        | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+


CentOS Stream 10
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)

CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

Fedora 41
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Fedora 41 (Clang)
	Kernel: Depends on container host
	Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.8 (Fedora 18.1.8-1.fc40)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

RHEL8
	Kernel: Depends on container host
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

Ubuntu 22.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 24.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-05-22 19:38 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250522074242.30376-1-sunyang.wu@jaguarmicro.com>
2025-05-22  7:09 ` |SUCCESS| pw153590 [PATCH v3] ethdev: fix the bug where the flag variables are assigned qemudev
2025-05-22  7:13 ` qemudev
2025-05-22  7:42 ` |WARNING| " checkpatch
2025-05-22  9:03 ` |SUCCESS| " 0-day Robot
2025-05-22 13:07 ` |SUCCESS| pw153590 [PATCH] [v3] ethdev: fix the bug where the flag v dpdklab
2025-05-22 13:17 ` dpdklab
2025-05-22 13:18 ` dpdklab
2025-05-22 13:19 ` dpdklab
2025-05-22 13:20 ` dpdklab
2025-05-22 13:22 ` dpdklab
2025-05-22 13:31 ` dpdklab
2025-05-22 13:34 ` dpdklab
2025-05-22 14:28 ` dpdklab
2025-05-22 14:29 ` dpdklab
2025-05-22 14:31 ` dpdklab
2025-05-22 14:42 ` |WARNING| " dpdklab
2025-05-22 14:42 ` |SUCCESS| " dpdklab
2025-05-22 14:45 ` dpdklab
2025-05-22 14:48 ` dpdklab
2025-05-22 14:57 ` dpdklab
2025-05-22 15:16 ` dpdklab
2025-05-22 15:16 ` |PENDING| " dpdklab
2025-05-22 15:23 ` dpdklab
2025-05-22 15:26 ` dpdklab
2025-05-22 15:41 ` |SUCCESS| " dpdklab
2025-05-22 15:57 ` |WARNING| " dpdklab
2025-05-22 15:57 ` dpdklab
2025-05-22 16:38 ` |PENDING| " dpdklab
2025-05-22 16:41 ` dpdklab
2025-05-22 16:50 ` dpdklab
2025-05-22 16:53 ` |FAILURE| " dpdklab
2025-05-22 17:16 ` |WARNING| " dpdklab
2025-05-22 17:27 ` |SUCCESS| " dpdklab
2025-05-22 17:29 ` |FAILURE| " dpdklab
2025-05-22 17:37 ` dpdklab
2025-05-22 18:11 ` dpdklab
2025-05-22 18:47 ` dpdklab
2025-05-22 18:57 ` dpdklab
2025-05-22 19:02 ` dpdklab
2025-05-22 19:07 ` dpdklab
2025-05-22 19:29 ` dpdklab
2025-05-22 19:38 ` dpdklab [this message]
2025-05-22 19:43 ` |SUCCESS| " dpdklab
2025-05-22 20:28 ` dpdklab
2025-05-22 21:37 ` dpdklab
2025-05-22 22:04 ` 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=682f7d27.050a0220.197c1c.1bbdSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --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).