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| pw140857-140859 [PATCH] [v8,3/3] net/mlx5: implement VXLAN
Date: Fri, 07 Jun 2024 13:25:31 -0700 (PDT)	[thread overview]
Message-ID: <66636cbb.4a0a0220.82859.a8dfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240607140208.315235-4-rongweil@nvidia.com>

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

_Testing PASS_

Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Friday, June 07 2024 14:02:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a6bbf008457a455fcf4cf7374c280bba697a353f

140857-140859 --> testing pass

Test environment and result as below:

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


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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

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

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

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

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

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

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

Ubuntu 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

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

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-07 20:25 UTC|newest]

Thread overview: 94+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240607140208.315235-4-rongweil@nvidia.com>
2024-06-07 13:36 ` |SUCCESS| pw140857-140859 [PATCH v8 3/3] net/mlx5: implement VXLAN last reserved modification qemudev
2024-06-07 13:40 ` qemudev
2024-06-07 14:04 ` |SUCCESS| pw140859 " checkpatch
2024-06-07 15:25 ` 0-day Robot
2024-06-07 17:17 ` |SUCCESS| pw140857-140859 [PATCH] [v8,3/3] net/mlx5: implement VXLAN dpdklab
2024-06-07 17:28 ` dpdklab
2024-06-07 17:29 ` dpdklab
2024-06-07 17:35 ` dpdklab
2024-06-07 17:35 ` dpdklab
2024-06-07 17:45 ` dpdklab
2024-06-07 17:46 ` dpdklab
2024-06-07 17:47 ` dpdklab
2024-06-07 17:52 ` dpdklab
2024-06-07 17:53 ` dpdklab
2024-06-07 17:55 ` dpdklab
2024-06-07 17:56 ` dpdklab
2024-06-07 17:56 ` dpdklab
2024-06-07 17:57 ` dpdklab
2024-06-07 18:15 ` dpdklab
2024-06-07 18:16 ` dpdklab
2024-06-07 18:16 ` dpdklab
2024-06-07 18:20 ` dpdklab
2024-06-07 18:21 ` dpdklab
2024-06-07 18:22 ` dpdklab
2024-06-07 18:25 ` dpdklab
2024-06-07 18:29 ` dpdklab
2024-06-07 18:41 ` dpdklab
2024-06-07 18:41 ` dpdklab
2024-06-07 18:42 ` dpdklab
2024-06-07 18:50 ` dpdklab
2024-06-07 18:52 ` dpdklab
2024-06-07 18:54 ` dpdklab
2024-06-07 18:56 ` dpdklab
2024-06-07 18:56 ` dpdklab
2024-06-07 18:57 ` dpdklab
2024-06-07 19:01 ` dpdklab
2024-06-07 19:16 ` dpdklab
2024-06-07 19:28 ` dpdklab
2024-06-07 19:52 ` dpdklab
2024-06-07 20:02 ` dpdklab
2024-06-07 20:03 ` dpdklab
2024-06-07 20:12 ` dpdklab
2024-06-07 20:16 ` dpdklab
2024-06-07 20:17 ` dpdklab
2024-06-07 20:17 ` dpdklab
2024-06-07 20:17 ` dpdklab
2024-06-07 20:18 ` dpdklab
2024-06-07 20:18 ` dpdklab
2024-06-07 20:18 ` dpdklab
2024-06-07 20:19 ` dpdklab
2024-06-07 20:19 ` dpdklab
2024-06-07 20:20 ` dpdklab
2024-06-07 20:20 ` dpdklab
2024-06-07 20:20 ` dpdklab
2024-06-07 20:21 ` dpdklab
2024-06-07 20:21 ` dpdklab
2024-06-07 20:22 ` dpdklab
2024-06-07 20:24 ` dpdklab
2024-06-07 20:25 ` dpdklab
2024-06-07 20:25 ` dpdklab [this message]
2024-06-07 20:26 ` dpdklab
2024-06-07 20:30 ` dpdklab
2024-06-07 20:30 ` dpdklab
2024-06-07 20:30 ` dpdklab
2024-06-07 20:31 ` dpdklab
2024-06-07 20:31 ` dpdklab
2024-06-07 20:38 ` dpdklab
2024-06-07 20:38 ` dpdklab
2024-06-07 20:39 ` dpdklab
2024-06-07 20:40 ` dpdklab
2024-06-07 20:40 ` dpdklab
2024-06-07 20:41 ` dpdklab
2024-06-07 20:41 ` dpdklab
2024-06-07 20:43 ` dpdklab
2024-06-07 20:43 ` dpdklab
2024-06-07 20:44 ` dpdklab
2024-06-07 20:44 ` dpdklab
2024-06-07 20:48 ` dpdklab
2024-06-07 20:50 ` dpdklab
2024-06-07 20:52 ` dpdklab
2024-06-07 20:57 ` dpdklab
2024-06-07 21:01 ` dpdklab
2024-06-07 21:02 ` dpdklab
2024-06-07 21:05 ` dpdklab
2024-06-07 21:06 ` dpdklab
2024-06-07 21:09 ` dpdklab
2024-06-07 21:11 ` dpdklab
2024-06-07 21:19 ` dpdklab
2024-06-07 21:25 ` dpdklab
2024-06-07 21:25 ` dpdklab
2024-06-07 21:26 ` dpdklab
2024-06-07 21:28 ` dpdklab
2024-06-07 21:39 ` dpdklab
2024-06-07 22:11 ` 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=66636cbb.4a0a0220.82859.a8dfSMTPIN_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).