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| pw141122 [PATCH] net/mlx5: fix mlx5 device start failure
Date: Thu, 13 Jun 2024 10:46:51 -0700 (PDT)	[thread overview]
Message-ID: <666b308b.050a0220.84575.48efSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240613124528.547952-1-bingz@nvidia.com>

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

_Testing PASS_

Submitter: Bing Zhao <bingz@nvidia.com>
Date: Thursday, June 13 2024 12:45:28 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c1cdfbcc339c2c951bff95854983a8773d9e5b8e

141122 --> testing pass

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| CentOS Stream 9  | PASS           |
+------------------+----------------+
| CentOS Stream 8  | PASS           |
+------------------+----------------+
| Debian Bullseye  | PASS           |
+------------------+----------------+
| Debian 12        | PASS           |
+------------------+----------------+
| Fedora 37        | PASS           |
+------------------+----------------+
| Fedora 38        | PASS           |
+------------------+----------------+
| openSUSE Leap 15 | PASS           |
+------------------+----------------+
| Fedora 39        | PASS           |
+------------------+----------------+
| RHEL8            | PASS           |
+------------------+----------------+
| Ubuntu 22.04     | PASS           |
+------------------+----------------+
| Ubuntu 20.04     | PASS           |
+------------------+----------------+
| RHEL9            | PASS           |
+------------------+----------------+


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

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

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

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

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

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

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

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

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-13 17:46 UTC|newest]

Thread overview: 104+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240613124528.547952-1-bingz@nvidia.com>
2024-06-13 12:23 ` qemudev
2024-06-13 12:27 ` qemudev
2024-06-13 12:46 ` checkpatch
2024-06-13 13:44 ` 0-day Robot
2024-06-13 15:56 ` dpdklab
2024-06-13 15:59 ` dpdklab
2024-06-13 16:00 ` dpdklab
2024-06-13 16:00 ` dpdklab
2024-06-13 16:01 ` dpdklab
2024-06-13 16:01 ` dpdklab
2024-06-13 16:03 ` dpdklab
2024-06-13 16:04 ` dpdklab
2024-06-13 16:05 ` dpdklab
2024-06-13 16:05 ` dpdklab
2024-06-13 16:07 ` dpdklab
2024-06-13 16:07 ` dpdklab
2024-06-13 16:07 ` dpdklab
2024-06-13 16:08 ` dpdklab
2024-06-13 16:44 ` dpdklab
2024-06-13 16:45 ` dpdklab
2024-06-13 16:46 ` dpdklab
2024-06-13 16:46 ` dpdklab
2024-06-13 16:46 ` dpdklab
2024-06-13 16:47 ` dpdklab
2024-06-13 16:48 ` dpdklab
2024-06-13 16:48 ` dpdklab
2024-06-13 16:48 ` dpdklab
2024-06-13 16:50 ` dpdklab
2024-06-13 16:50 ` dpdklab
2024-06-13 16:50 ` dpdklab
2024-06-13 16:51 ` dpdklab
2024-06-13 16:52 ` dpdklab
2024-06-13 16:52 ` dpdklab
2024-06-13 17:08 ` dpdklab
2024-06-13 17:27 ` dpdklab
2024-06-13 17:30 ` dpdklab
2024-06-13 17:33 ` dpdklab
2024-06-13 17:33 ` dpdklab
2024-06-13 17:34 ` dpdklab
2024-06-13 17:34 ` dpdklab
2024-06-13 17:35 ` dpdklab
2024-06-13 17:35 ` dpdklab
2024-06-13 17:36 ` dpdklab
2024-06-13 17:36 ` dpdklab
2024-06-13 17:36 ` dpdklab
2024-06-13 17:37 ` dpdklab
2024-06-13 17:37 ` dpdklab
2024-06-13 17:38 ` dpdklab
2024-06-13 17:39 ` dpdklab
2024-06-13 17:39 ` dpdklab
2024-06-13 17:40 ` dpdklab
2024-06-13 17:40 ` dpdklab
2024-06-13 17:40 ` dpdklab
2024-06-13 17:41 ` dpdklab
2024-06-13 17:41 ` dpdklab
2024-06-13 17:41 ` dpdklab
2024-06-13 17:42 ` dpdklab
2024-06-13 17:42 ` dpdklab
2024-06-13 17:42 ` dpdklab
2024-06-13 17:42 ` dpdklab
2024-06-13 17:43 ` dpdklab
2024-06-13 17:43 ` dpdklab
2024-06-13 17:43 ` dpdklab
2024-06-13 17:43 ` dpdklab
2024-06-13 17:43 ` dpdklab
2024-06-13 17:44 ` dpdklab
2024-06-13 17:44 ` dpdklab
2024-06-13 17:44 ` dpdklab
2024-06-13 17:44 ` dpdklab
2024-06-13 17:44 ` dpdklab
2024-06-13 17:44 ` dpdklab
2024-06-13 17:45 ` dpdklab
2024-06-13 17:45 ` dpdklab
2024-06-13 17:45 ` dpdklab
2024-06-13 17:45 ` dpdklab
2024-06-13 17:45 ` dpdklab
2024-06-13 17:45 ` dpdklab
2024-06-13 17:46 ` dpdklab
2024-06-13 17:46 ` dpdklab
2024-06-13 17:46 ` dpdklab
2024-06-13 17:46 ` dpdklab
2024-06-13 17:46 ` dpdklab
2024-06-13 17:46 ` dpdklab [this message]
2024-06-13 17:46 ` dpdklab
2024-06-13 17:47 ` dpdklab
2024-06-13 17:48 ` dpdklab
2024-06-13 17:48 ` dpdklab
2024-06-13 17:48 ` dpdklab
2024-06-13 17:49 ` dpdklab
2024-06-13 17:49 ` dpdklab
2024-06-13 17:51 ` dpdklab
2024-06-13 17:52 ` dpdklab
2024-06-13 17:54 ` dpdklab
2024-06-13 17:56 ` dpdklab
2024-06-13 17:58 ` dpdklab
2024-06-13 18:01 ` dpdklab
2024-06-13 18:01 ` dpdklab
2024-06-13 18:02 ` dpdklab
2024-06-13 18:04 ` dpdklab
2024-06-13 18:10 ` dpdklab
2024-06-13 18:11 ` dpdklab
2024-06-13 18:19 ` dpdklab
2024-06-13 20:11 ` dpdklab
2024-06-13 20:14 ` 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=666b308b.050a0220.84575.48efSMTPIN_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).