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| pw140721-140723 [PATCH] [v3,3/3] net/mlx5: implement VXLAN
Date: Tue, 04 Jun 2024 07:21:19 -0700 (PDT)	[thread overview]
Message-ID: <665f22df.050a0220.65e73.f6c2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240604121502.376102-4-rongweil@nvidia.com>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140723

_Testing PASS_

Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Tuesday, June 04 2024 12:15:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a6bbf008457a455fcf4cf7374c280bba697a353f

140721-140723 --> testing pass

Test environment and result as below:

+-----------------------------+----------------+--------------+
|         Environment         | dpdk_unit_test | lpm_autotest |
+=============================+================+==============+
| 32-bit Ubuntu 20.04.4 (ARM) | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Debian 12 (arm)             | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| CentOS Stream 9 (ARM)       | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Fedora 39 (ARM)             | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Fedora 38 (ARM Clang)       | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Fedora 37 (ARM)             | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Fedora 38 (ARM)             | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE        | SKIPPED        | PASS         |
+-----------------------------+----------------+--------------+


32-bit Ubuntu 20.04.4 (ARM)
	Kernel: 5.4.0-155-generic aarch64
	Compiler: gcc 9.4

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.1

Fedora 39 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

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

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 14:21 UTC|newest]

Thread overview: 97+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240604121502.376102-4-rongweil@nvidia.com>
2024-06-04 11:49 ` |SUCCESS| pw140721-140723 [PATCH v3 3/3] net/mlx5: implement VXLAN last reserved modification qemudev
2024-06-04 11:53 ` qemudev
2024-06-04 12:18 ` |SUCCESS| pw140723 " checkpatch
2024-06-04 13:02 ` |SUCCESS| pw140721-140723 [PATCH] [v3,3/3] net/mlx5: implement VXLAN dpdklab
2024-06-04 13:03 ` dpdklab
2024-06-04 13:04 ` dpdklab
2024-06-04 13:04 ` dpdklab
2024-06-04 13:14 ` dpdklab
2024-06-04 13:14 ` dpdklab
2024-06-04 13:15 ` dpdklab
2024-06-04 13:15 ` dpdklab
2024-06-04 13:15 ` dpdklab
2024-06-04 13:16 ` dpdklab
2024-06-04 13:16 ` dpdklab
2024-06-04 13:17 ` dpdklab
2024-06-04 13:17 ` dpdklab
2024-06-04 13:17 ` dpdklab
2024-06-04 13:18 ` dpdklab
2024-06-04 13:18 ` dpdklab
2024-06-04 13:19 ` dpdklab
2024-06-04 13:24 ` dpdklab
2024-06-04 13:25 ` dpdklab
2024-06-04 13:25 ` dpdklab
2024-06-04 13:25 ` dpdklab
2024-06-04 13:25 ` dpdklab
2024-06-04 13:26 ` dpdklab
2024-06-04 13:26 ` dpdklab
2024-06-04 13:27 ` dpdklab
2024-06-04 13:27 ` dpdklab
2024-06-04 13:28 ` dpdklab
2024-06-04 13:28 ` dpdklab
2024-06-04 13:28 ` dpdklab
2024-06-04 13:29 ` dpdklab
2024-06-04 13:29 ` dpdklab
2024-06-04 13:29 ` dpdklab
2024-06-04 13:29 ` dpdklab
2024-06-04 13:30 ` dpdklab
2024-06-04 13:33 ` dpdklab
2024-06-04 13:33 ` dpdklab
2024-06-04 13:34 ` dpdklab
2024-06-04 13:34 ` dpdklab
2024-06-04 13:34 ` dpdklab
2024-06-04 13:35 ` dpdklab
2024-06-04 13:35 ` dpdklab
2024-06-04 13:36 ` dpdklab
2024-06-04 13:44 ` dpdklab
2024-06-04 13:45 ` dpdklab
2024-06-04 13:46 ` dpdklab
2024-06-04 13:46 ` dpdklab
2024-06-04 13:46 ` dpdklab
2024-06-04 13:46 ` dpdklab
2024-06-04 13:47 ` dpdklab
2024-06-04 13:47 ` dpdklab
2024-06-04 13:47 ` dpdklab
2024-06-04 13:48 ` dpdklab
2024-06-04 13:48 ` dpdklab
2024-06-04 13:48 ` dpdklab
2024-06-04 13:48 ` dpdklab
2024-06-04 13:48 ` dpdklab
2024-06-04 13:50 ` dpdklab
2024-06-04 13:50 ` dpdklab
2024-06-04 13:50 ` dpdklab
2024-06-04 13:51 ` dpdklab
2024-06-04 13:53 ` dpdklab
2024-06-04 13:56 ` dpdklab
2024-06-04 13:58 ` dpdklab
2024-06-04 14:00 ` dpdklab
2024-06-04 14:03 ` dpdklab
2024-06-04 14:03 ` dpdklab
2024-06-04 14:03 ` dpdklab
2024-06-04 14:03 ` dpdklab
2024-06-04 14:04 ` dpdklab
2024-06-04 14:04 ` dpdklab
2024-06-04 14:07 ` dpdklab
2024-06-04 14:09 ` dpdklab
2024-06-04 14:10 ` dpdklab
2024-06-04 14:10 ` dpdklab
2024-06-04 14:13 ` dpdklab
2024-06-04 14:14 ` dpdklab
2024-06-04 14:19 ` dpdklab
2024-06-04 14:19 ` dpdklab
2024-06-04 14:20 ` dpdklab
2024-06-04 14:20 ` dpdklab
2024-06-04 14:21 ` dpdklab [this message]
2024-06-04 14:23 ` dpdklab
2024-06-04 14:25 ` dpdklab
2024-06-04 14:30 ` dpdklab
2024-06-04 14:31 ` dpdklab
2024-06-04 14:46 ` dpdklab
2024-06-04 14:55 ` dpdklab
2024-06-04 14:58 ` dpdklab
2024-06-04 15:01 ` dpdklab
2024-06-04 15:06 ` dpdklab
2024-06-04 15:12 ` dpdklab
2024-06-04 15:28 ` dpdklab
2024-06-04 15:54 ` dpdklab
2024-06-04 16:20 ` 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=665f22df.050a0220.65e73.f6c2SMTPIN_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).