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| pw139426-139427 [PATCH] [4/4] net/mlx5/hws: remove table t
Date: Tue, 16 Apr 2024 15:17:09 -0700 (PDT)	[thread overview]
Message-ID: <661ef8e5.050a0220.12d11.f89bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240416153054.3216706-5-michaelba@nvidia.com>

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

_Testing PASS_

Submitter: Michael Baum <michaelba@nvidia.com>
Date: Tuesday, April 16 2024 15:30:54 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2

139426-139427 --> testing pass

Test environment and result as below:

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


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

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 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

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

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)

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

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/29794/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-16 22:17 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240416153054.3216706-5-michaelba@nvidia.com>
2024-04-16 15:17 ` |SUCCESS| pw139426-139427 [PATCH 4/4] net/mlx5/hws: remove table type DONTCARE qemudev
2024-04-16 15:22 ` qemudev
2024-04-16 15:33 ` |SUCCESS| pw139427 " checkpatch
2024-04-16 16:24 ` 0-day Robot
2024-04-16 20:18 ` |SUCCESS| pw139426-139427 [PATCH] [4/4] net/mlx5/hws: remove table t dpdklab
2024-04-16 20:42 ` dpdklab
2024-04-16 20:43 ` dpdklab
2024-04-16 20:48 ` dpdklab
2024-04-16 20:49 ` dpdklab
2024-04-16 20:49 ` dpdklab
2024-04-16 20:50 ` dpdklab
2024-04-16 20:50 ` dpdklab
2024-04-16 20:52 ` dpdklab
2024-04-16 20:52 ` dpdklab
2024-04-16 20:53 ` dpdklab
2024-04-16 20:53 ` dpdklab
2024-04-16 20:53 ` dpdklab
2024-04-16 20:53 ` dpdklab
2024-04-16 21:10 ` dpdklab
2024-04-16 21:19 ` dpdklab
2024-04-16 21:19 ` dpdklab
2024-04-16 21:20 ` dpdklab
2024-04-16 21:27 ` dpdklab
2024-04-16 21:28 ` dpdklab
2024-04-16 21:29 ` dpdklab
2024-04-16 21:33 ` dpdklab
2024-04-16 21:38 ` dpdklab
2024-04-16 21:40 ` dpdklab
2024-04-16 21:40 ` dpdklab
2024-04-16 21:41 ` dpdklab
2024-04-16 21:42 ` dpdklab
2024-04-16 21:42 ` dpdklab
2024-04-16 21:42 ` dpdklab
2024-04-16 21:42 ` dpdklab
2024-04-16 21:43 ` dpdklab
2024-04-16 21:43 ` dpdklab
2024-04-16 21:44 ` dpdklab
2024-04-16 21:44 ` dpdklab
2024-04-16 21:44 ` dpdklab
2024-04-16 21:45 ` dpdklab
2024-04-16 21:45 ` dpdklab
2024-04-16 21:45 ` dpdklab
2024-04-16 21:46 ` dpdklab
2024-04-16 21:46 ` dpdklab
2024-04-16 21:46 ` dpdklab
2024-04-16 21:46 ` dpdklab
2024-04-16 21:46 ` dpdklab
2024-04-16 21:46 ` dpdklab
2024-04-16 21:47 ` dpdklab
2024-04-16 21:47 ` dpdklab
2024-04-16 21:47 ` dpdklab
2024-04-16 21:47 ` dpdklab
2024-04-16 21:47 ` dpdklab
2024-04-16 21:48 ` dpdklab
2024-04-16 21:48 ` dpdklab
2024-04-16 21:48 ` dpdklab
2024-04-16 21:48 ` dpdklab
2024-04-16 21:49 ` dpdklab
2024-04-16 21:49 ` dpdklab
2024-04-16 21:49 ` dpdklab
2024-04-16 21:49 ` dpdklab
2024-04-16 21:49 ` dpdklab
2024-04-16 21:49 ` dpdklab
2024-04-16 21:49 ` dpdklab
2024-04-16 21:50 ` dpdklab
2024-04-16 21:50 ` dpdklab
2024-04-16 21:50 ` dpdklab
2024-04-16 21:50 ` dpdklab
2024-04-16 21:51 ` dpdklab
2024-04-16 21:51 ` dpdklab
2024-04-16 21:51 ` dpdklab
2024-04-16 21:53 ` dpdklab
2024-04-16 21:54 ` dpdklab
2024-04-16 21:56 ` dpdklab
2024-04-16 21:56 ` dpdklab
2024-04-16 21:58 ` dpdklab
2024-04-16 21:58 ` dpdklab
2024-04-16 22:05 ` dpdklab
2024-04-16 22:09 ` dpdklab
2024-04-16 22:17 ` dpdklab [this message]
2024-04-16 22:29 ` dpdklab
2024-04-16 22:41 ` dpdklab
2024-04-16 22:43 ` dpdklab
2024-04-16 22:45 ` dpdklab
2024-04-16 22:49 ` dpdklab
2024-04-16 22:50 ` dpdklab
2024-04-16 22:50 ` dpdklab
2024-04-16 22:54 ` dpdklab
2024-04-16 23:13 ` dpdklab
2024-04-17  0:07 ` dpdklab
2024-04-17  1:00 ` 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=661ef8e5.050a0220.12d11.f89bSMTPIN_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).