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| pw140725-140724 [PATCH] [v4,3/3] net/mlx5: implement VXLAN
Date: Tue, 04 Jun 2024 10:28:58 -0700 (PDT)	[thread overview]
Message-ID: <665f4eda.050a0220.1de7bf.0cb6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240604123840.432044-4-rongweil@nvidia.com>

Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140724

_Testing PASS_

Submitter: rongwei liu <rongweil@nvidia.com>
Date: Tuesday, June 04 2024 12:38:39 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a6bbf008457a455fcf4cf7374c280bba697a353f

140725-140724 --> testing pass

Test environment and result as below:

+-----------------+----------+
|   Environment   | abi_test |
+=================+==========+
| CentOS Stream 9 | PASS     |
+-----------------+----------+
| Debian Bullseye | PASS     |
+-----------------+----------+
| Fedora 38       | PASS     |
+-----------------+----------+
| Debian 12       | PASS     |
+-----------------+----------+


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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

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-04 17:29 UTC|newest]

Thread overview: 100+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240604123840.432044-4-rongweil@nvidia.com>
2024-06-04 12:21 ` |SUCCESS| pw140725-140724 [PATCH v4 3/3] net/mlx5: implement VXLAN last reserved modification qemudev
2024-06-04 12:25 ` qemudev
2024-06-04 12:40 ` |SUCCESS| pw140724 " checkpatch
2024-06-04 13:45 ` 0-day Robot
2024-06-04 16:24 ` |SUCCESS| pw140725-140724 [PATCH] [v4,3/3] net/mlx5: implement VXLAN dpdklab
2024-06-04 16:26 ` dpdklab
2024-06-04 16:37 ` dpdklab
2024-06-04 16:41 ` dpdklab
2024-06-04 17:13 ` dpdklab
2024-06-04 17:13 ` dpdklab
2024-06-04 17:17 ` dpdklab
2024-06-04 17:18 ` dpdklab
2024-06-04 17:19 ` dpdklab
2024-06-04 17:19 ` dpdklab
2024-06-04 17:19 ` dpdklab
2024-06-04 17:20 ` dpdklab
2024-06-04 17:20 ` dpdklab
2024-06-04 17:23 ` dpdklab
2024-06-04 17:23 ` dpdklab
2024-06-04 17:23 ` dpdklab
2024-06-04 17:24 ` dpdklab
2024-06-04 17:28 ` dpdklab [this message]
2024-06-04 17:31 ` dpdklab
2024-06-04 17:38 ` dpdklab
2024-06-04 17:38 ` dpdklab
2024-06-04 17:39 ` dpdklab
2024-06-04 17:41 ` dpdklab
2024-06-04 17:44 ` dpdklab
2024-06-04 17:45 ` dpdklab
2024-06-04 17:47 ` dpdklab
2024-06-04 17:50 ` dpdklab
2024-06-04 17:51 ` dpdklab
2024-06-04 17:52 ` dpdklab
2024-06-04 17:55 ` dpdklab
2024-06-04 17:56 ` dpdklab
2024-06-04 17:57 ` dpdklab
2024-06-04 18:00 ` dpdklab
2024-06-04 18:00 ` dpdklab
2024-06-04 18:01 ` dpdklab
2024-06-04 18:04 ` dpdklab
2024-06-04 18:15 ` dpdklab
2024-06-04 18:23 ` dpdklab
2024-06-04 18:24 ` dpdklab
2024-06-04 18:28 ` dpdklab
2024-06-04 18:29 ` dpdklab
2024-06-04 18:34 ` dpdklab
2024-06-04 18:34 ` dpdklab
2024-06-04 18:35 ` dpdklab
2024-06-04 18:37 ` dpdklab
2024-06-04 18:41 ` dpdklab
2024-06-04 18:44 ` dpdklab
2024-06-04 18:45 ` dpdklab
2024-06-04 18:48 ` dpdklab
2024-06-04 18:49 ` dpdklab
2024-06-04 18:49 ` dpdklab
2024-06-04 18:50 ` dpdklab
2024-06-04 18:53 ` dpdklab
2024-06-04 18:53 ` dpdklab
2024-06-04 19:03 ` dpdklab
2024-06-04 19:03 ` dpdklab
2024-06-04 19:04 ` dpdklab
2024-06-04 19:04 ` dpdklab
2024-06-04 19:04 ` dpdklab
2024-06-04 19:05 ` dpdklab
2024-06-04 19:05 ` dpdklab
2024-06-04 19:05 ` dpdklab
2024-06-04 19:06 ` dpdklab
2024-06-04 19:06 ` dpdklab
2024-06-04 19:06 ` dpdklab
2024-06-04 19:06 ` dpdklab
2024-06-04 19:07 ` dpdklab
2024-06-04 19:28 ` dpdklab
2024-06-04 19:29 ` dpdklab
2024-06-04 19:29 ` dpdklab
2024-06-04 19:29 ` dpdklab
2024-06-04 19:30 ` dpdklab
2024-06-04 19:30 ` dpdklab
2024-06-04 19:32 ` dpdklab
2024-06-04 19:32 ` dpdklab
2024-06-04 19:32 ` dpdklab
2024-06-04 19:32 ` dpdklab
2024-06-04 19:33 ` dpdklab
2024-06-04 19:33 ` dpdklab
2024-06-04 19:34 ` dpdklab
2024-06-04 19:34 ` dpdklab
2024-06-04 19:36 ` dpdklab
2024-06-04 19:36 ` dpdklab
2024-06-04 19:39 ` dpdklab
2024-06-04 19:39 ` dpdklab
2024-06-04 19:43 ` dpdklab
2024-06-04 19:56 ` dpdklab
2024-06-04 20:03 ` dpdklab
2024-06-04 20:05 ` dpdklab
2024-06-04 20:09 ` dpdklab
2024-06-04 20:09 ` dpdklab
2024-06-04 20:10 ` dpdklab
2024-06-04 20:36 ` dpdklab
2024-06-04 20:36 ` dpdklab
2024-06-04 21:50 ` dpdklab
2024-06-04 21:59 ` 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=665f4eda.050a0220.1de7bf.0cb6SMTPIN_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).