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| pw138766 [PATCH] [v2] app/testpmd: fix releasing action ha
Date: Mon, 25 Mar 2024 11:51:24 -0700 (PDT)	[thread overview]
Message-ID: <6601c7ac.170a0220.cf150.d69aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240325105826.393231-1-bingz@nvidia.com>

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

_Testing PASS_

Submitter: Bing Zhao <bingz@nvidia.com>
Date: Monday, March 25 2024 10:58:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3ce30fc646084443eb06eb808c73e3312edc90d1

138766 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| Debian 11 (arm)     | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+


Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

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

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

Debian 11 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-25 18:51 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240325105826.393231-1-bingz@nvidia.com>
2024-03-25 10:35 ` |SUCCESS| pw138766 [PATCH v2] app/testpmd: fix releasing action handle flush memory qemudev
2024-03-25 10:40 ` qemudev
2024-03-25 10:59 ` checkpatch
2024-03-25 12:04 ` 0-day Robot
2024-03-25 17:34 ` |SUCCESS| pw138766 [PATCH] [v2] app/testpmd: fix releasing action ha dpdklab
2024-03-25 17:36 ` dpdklab
2024-03-25 17:37 ` dpdklab
2024-03-25 17:40 ` dpdklab
2024-03-25 18:01 ` dpdklab
2024-03-25 18:02 ` dpdklab
2024-03-25 18:02 ` dpdklab
2024-03-25 18:03 ` dpdklab
2024-03-25 18:03 ` dpdklab
2024-03-25 18:03 ` dpdklab
2024-03-25 18:04 ` dpdklab
2024-03-25 18:04 ` dpdklab
2024-03-25 18:06 ` dpdklab
2024-03-25 18:06 ` dpdklab
2024-03-25 18:07 ` dpdklab
2024-03-25 18:07 ` dpdklab
2024-03-25 18:07 ` dpdklab
2024-03-25 18:07 ` dpdklab
2024-03-25 18:08 ` dpdklab
2024-03-25 18:08 ` dpdklab
2024-03-25 18:09 ` dpdklab
2024-03-25 18:09 ` dpdklab
2024-03-25 18:09 ` dpdklab
2024-03-25 18:09 ` dpdklab
2024-03-25 18:10 ` dpdklab
2024-03-25 18:10 ` dpdklab
2024-03-25 18:10 ` dpdklab
2024-03-25 18:10 ` dpdklab
2024-03-25 18:11 ` dpdklab
2024-03-25 18:11 ` dpdklab
2024-03-25 18:11 ` dpdklab
2024-03-25 18:11 ` dpdklab
2024-03-25 18:12 ` dpdklab
2024-03-25 18:12 ` dpdklab
2024-03-25 18:12 ` dpdklab
2024-03-25 18:13 ` dpdklab
2024-03-25 18:13 ` dpdklab
2024-03-25 18:13 ` dpdklab
2024-03-25 18:13 ` dpdklab
2024-03-25 18:13 ` dpdklab
2024-03-25 18:13 ` dpdklab
2024-03-25 18:14 ` dpdklab
2024-03-25 18:14 ` dpdklab
2024-03-25 18:17 ` dpdklab
2024-03-25 18:18 ` dpdklab
2024-03-25 18:19 ` dpdklab
2024-03-25 18:23 ` dpdklab
2024-03-25 18:24 ` dpdklab
2024-03-25 18:24 ` dpdklab
2024-03-25 18:25 ` dpdklab
2024-03-25 18:29 ` dpdklab
2024-03-25 18:30 ` dpdklab
2024-03-25 18:30 ` dpdklab
2024-03-25 18:31 ` dpdklab
2024-03-25 18:31 ` dpdklab
2024-03-25 18:49 ` dpdklab
2024-03-25 18:49 ` dpdklab
2024-03-25 18:49 ` dpdklab
2024-03-25 18:50 ` dpdklab
2024-03-25 18:51 ` dpdklab [this message]
2024-03-25 18:51 ` dpdklab
2024-03-25 18:54 ` dpdklab
2024-03-25 18:55 ` dpdklab
2024-03-25 18:56 ` dpdklab
2024-03-25 18:57 ` dpdklab
2024-03-25 18:57 ` dpdklab
2024-03-25 19:03 ` dpdklab
2024-03-25 19:15 ` dpdklab
2024-03-25 19:31 ` dpdklab
2024-03-25 19:50 ` dpdklab
2024-03-25 20:12 ` dpdklab
2024-04-01 15:45 ` dpdklab
2024-04-01 15:49 ` dpdklab
2024-04-01 15:53 ` dpdklab
2024-04-01 15:57 ` dpdklab
2024-04-01 16:16 ` 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=6601c7ac.170a0220.cf150.d69aSMTPIN_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).