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| pw141205-141206 [PATCH] [2/2] net/mlx5: fix non-template I
Date: Mon, 17 Jun 2024 07:55:12 -0700 (PDT)	[thread overview]
Message-ID: <66704e50.050a0220.2c6fe.f989SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240617140747.169197-3-getelson@nvidia.com>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/141206

_Functional Testing PASS_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Monday, June 17 2024 14:07:47 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c1cdfbcc339c2c951bff95854983a8773d9e5b8e

141205-141206 --> functional testing pass

Test environment and result as below:

Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 11.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: Unknown

Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter    |  PASS  |
+------------+--------+


Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: Unknown

Aggregate Results by Test Suite
+-----------------------------+--------+
|         Test Suite          | Result |
+=============================+========+
| scatter                     |  PASS  |
+-----------------------------+--------+
| unit_tests_mbuf             |  PASS  |
+-----------------------------+--------+
| vhost_virtio_user_interrupt |  PASS  |
+-----------------------------+--------+
| virtio_smoke                |  PASS  |
+-----------------------------+--------+


Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: Unknown

Aggregate Results by Test Suite
+-----------------+--------+
|   Test Suite    | Result |
+=================+========+
| mtu_update      |  PASS  |
+-----------------+--------+
| unit_tests_mbuf |  PASS  |
+-----------------+--------+


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

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

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240617140747.169197-3-getelson@nvidia.com>
2024-06-17 13:44 ` |SUCCESS| pw141205-141206 [PATCH 2/2] net/mlx5: fix non-template IPv6 RSS hash qemudev
2024-06-17 13:48 ` qemudev
2024-06-17 14:10 ` |SUCCESS| pw141206 " checkpatch
2024-06-17 14:54 ` |SUCCESS| pw141205-141206 [PATCH] [2/2] net/mlx5: fix non-template I dpdklab
2024-06-17 14:54 ` dpdklab
2024-06-17 14:54 ` dpdklab
2024-06-17 14:55 ` dpdklab [this message]
2024-06-17 14:55 ` dpdklab
2024-06-17 14:55 ` dpdklab
2024-06-17 14:55 ` dpdklab
2024-06-17 14:56 ` dpdklab
2024-06-17 14:56 ` dpdklab
2024-06-17 14:56 ` dpdklab
2024-06-17 14:56 ` dpdklab
2024-06-17 14:56 ` dpdklab
2024-06-17 14:56 ` dpdklab
2024-06-17 14:57 ` dpdklab
2024-06-17 14:57 ` dpdklab
2024-06-17 14:57 ` dpdklab
2024-06-17 14:57 ` dpdklab
2024-06-17 14:57 ` dpdklab
2024-06-17 14:58 ` dpdklab
2024-06-17 14:58 ` dpdklab
2024-06-17 14:58 ` dpdklab
2024-06-17 14:58 ` dpdklab
2024-06-17 15:05 ` dpdklab
2024-06-17 15:05 ` dpdklab
2024-06-17 15:06 ` dpdklab
2024-06-17 15:06 ` dpdklab
2024-06-17 15:06 ` dpdklab
2024-06-17 15:06 ` dpdklab
2024-06-17 15:10 ` dpdklab
2024-06-17 15:10 ` dpdklab
2024-06-17 15:10 ` dpdklab
2024-06-17 15:11 ` dpdklab
2024-06-17 15:11 ` dpdklab
2024-06-17 15:12 ` dpdklab
2024-06-17 15:12 ` dpdklab
2024-06-17 15:13 ` dpdklab
2024-06-17 15:13 ` dpdklab
2024-06-17 15:13 ` dpdklab
2024-06-17 15:14 ` dpdklab
2024-06-17 15:14 ` dpdklab
2024-06-17 15:18 ` dpdklab
2024-06-17 15:18 ` dpdklab
2024-06-17 15:19 ` dpdklab
2024-06-17 15:20 ` dpdklab
2024-06-17 15:23 ` dpdklab
2024-06-17 15:24 ` dpdklab
2024-06-17 15:39 ` dpdklab
2024-06-17 15:40 ` dpdklab
2024-06-17 15:40 ` dpdklab
2024-06-17 15:42 ` dpdklab
2024-06-17 15:42 ` dpdklab
2024-06-17 15:42 ` dpdklab
2024-06-17 15:43 ` dpdklab
2024-06-17 15:43 ` dpdklab
2024-06-17 15:44 ` dpdklab
2024-06-17 15:45 ` dpdklab
2024-06-17 15:45 ` dpdklab
2024-06-17 15:45 ` dpdklab
2024-06-17 15:46 ` dpdklab
2024-06-17 15:46 ` dpdklab
2024-06-17 15:46 ` dpdklab
2024-06-17 15:52 ` dpdklab
2024-06-17 15:53 ` dpdklab
2024-06-17 15:53 ` dpdklab
2024-06-17 15:53 ` dpdklab
2024-06-17 15:54 ` dpdklab
2024-06-17 15:54 ` dpdklab
2024-06-17 15:54 ` dpdklab
2024-06-17 15:55 ` dpdklab
2024-06-17 15:55 ` dpdklab
2024-06-17 15:55 ` dpdklab
2024-06-17 15:59 ` dpdklab
2024-06-17 16:00 ` dpdklab
2024-06-17 16:01 ` dpdklab
2024-06-17 16:05 ` dpdklab
2024-06-17 16:10 ` dpdklab
2024-06-17 16:10 ` dpdklab
2024-06-17 16:10 ` dpdklab
2024-06-17 16:11 ` dpdklab
2024-06-17 16:13 ` dpdklab
2024-06-17 16:14 ` dpdklab
2024-06-17 16:14 ` dpdklab
2024-06-17 16:18 ` dpdklab
2024-06-17 16:20 ` dpdklab
2024-06-17 16:20 ` dpdklab
2024-06-17 16:24 ` dpdklab
2024-06-17 16:25 ` dpdklab
2024-06-17 16:25 ` dpdklab
2024-06-17 16:27 ` dpdklab
2024-06-17 16:27 ` dpdklab
2024-06-17 16:28 ` dpdklab
2024-06-17 16:30 ` dpdklab
2024-06-17 16:30 ` dpdklab
2024-06-17 16:37 ` dpdklab
2024-06-17 16:49 ` dpdklab
2024-06-17 16:49 ` dpdklab
2024-06-17 16:51 ` dpdklab
2024-06-17 16:54 ` dpdklab
2024-06-17 16:56 ` dpdklab
2024-06-17 16:56 ` dpdklab
2024-06-17 16:58 ` dpdklab
2024-06-17 16:58 ` dpdklab
2024-06-17 16:59 ` dpdklab
2024-06-17 16:59 ` dpdklab
2024-06-17 17:01 ` dpdklab
2024-06-17 17:02 ` dpdklab
2024-06-17 17:27 ` 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=66704e50.050a0220.2c6fe.f989SMTPIN_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).