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| pw138732 [PATCH] maintainers: update for gve/igc/ntb drive
Date: Fri, 22 Mar 2024 00:28:00 -0700 (PDT)	[thread overview]
Message-ID: <65fd3300.050a0220.998c3.226dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240322135959.345397-1-junfeng.guo@intel.com>

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

_Testing PASS_

Submitter: Junfeng Guo <junfeng.guo@intel.com>
Date: Friday, March 22 2024 13:59:59 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:0219d467bcb1d19b386b5bae8eecd3514ba13fdb

138732 --> testing pass

Test environment and result as below:

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


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

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 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

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

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

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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

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

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

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-22  7:28 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240322135959.345397-1-junfeng.guo@intel.com>
2024-03-22  5:41 ` |SUCCESS| pw138732 [PATCH] maintainers: update for gve/igc/ntb drivers qemudev
2024-03-22  5:46 ` qemudev
2024-03-22  6:05 ` checkpatch
2024-03-22  6:54 ` |SUCCESS| pw138732 [PATCH] maintainers: update for gve/igc/ntb drive dpdklab
2024-03-22  6:57 ` dpdklab
2024-03-22  7:02 ` dpdklab
2024-03-22  7:03 ` dpdklab
2024-03-22  7:03 ` dpdklab
2024-03-22  7:04 ` dpdklab
2024-03-22  7:04 ` dpdklab
2024-03-22  7:05 ` |SUCCESS| pw138732 [PATCH] maintainers: update for gve/igc/ntb drivers 0-day Robot
2024-03-22  7:05 ` |SUCCESS| pw138732 [PATCH] maintainers: update for gve/igc/ntb drive dpdklab
2024-03-22  7:06 ` dpdklab
2024-03-22  7:06 ` dpdklab
2024-03-22  7:06 ` dpdklab
2024-03-22  7:06 ` dpdklab
2024-03-22  7:06 ` dpdklab
2024-03-22  7:07 ` dpdklab
2024-03-22  7:07 ` dpdklab
2024-03-22  7:07 ` dpdklab
2024-03-22  7:11 ` dpdklab
2024-03-22  7:11 ` dpdklab
2024-03-22  7:12 ` dpdklab
2024-03-22  7:19 ` dpdklab
2024-03-22  7:20 ` dpdklab
2024-03-22  7:20 ` dpdklab
2024-03-22  7:20 ` dpdklab
2024-03-22  7:21 ` dpdklab
2024-03-22  7:21 ` dpdklab
2024-03-22  7:21 ` dpdklab
2024-03-22  7:21 ` dpdklab
2024-03-22  7:22 ` dpdklab
2024-03-22  7:22 ` dpdklab
2024-03-22  7:26 ` dpdklab
2024-03-22  7:26 ` dpdklab
2024-03-22  7:27 ` dpdklab
2024-03-22  7:27 ` dpdklab
2024-03-22  7:27 ` dpdklab
2024-03-22  7:28 ` dpdklab [this message]
2024-03-22  7:28 ` dpdklab
2024-03-22  7:28 ` dpdklab
2024-03-22  7:30 ` dpdklab
2024-03-22  7:30 ` dpdklab
2024-03-22  7:31 ` dpdklab
2024-03-22  7:32 ` dpdklab
2024-03-22  7:32 ` dpdklab
2024-03-22  7:33 ` dpdklab
2024-03-22  7:33 ` dpdklab
2024-03-22  7:34 ` dpdklab
2024-03-22  7:34 ` dpdklab
2024-03-22  7:34 ` dpdklab
2024-03-22  7:35 ` dpdklab
2024-03-22  7:35 ` dpdklab
2024-03-22  7:35 ` dpdklab
2024-03-22  7:37 ` dpdklab
2024-03-22  7:37 ` dpdklab
2024-03-22  7:37 ` dpdklab
2024-03-22  7:37 ` dpdklab
2024-03-22  7:38 ` dpdklab
2024-03-22  7:40 ` dpdklab
2024-03-22  7:40 ` dpdklab
2024-03-22  7:40 ` dpdklab
2024-03-22  7:41 ` dpdklab
2024-03-22  7:43 ` dpdklab
2024-03-22  7:45 ` dpdklab
2024-03-22  7:46 ` dpdklab
2024-03-22  7:47 ` dpdklab
2024-03-22  7:48 ` dpdklab
2024-03-22  7:49 ` dpdklab
2024-03-22  7:54 ` dpdklab
2024-03-22  7:55 ` dpdklab
2024-03-22  7:56 ` dpdklab
2024-03-22  7:57 ` dpdklab
2024-03-22  7:57 ` dpdklab
2024-03-22  8:10 ` dpdklab
2024-03-22  8:22 ` dpdklab
2024-03-22  8:32 ` dpdklab
2024-03-24  0:08 ` dpdklab
2024-03-24  0:44 ` 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=65fd3300.050a0220.998c3.226dSMTPIN_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).