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| pw140401-140408 [PATCH] [v6,8/8] test: update to latencyst
Date: Wed, 29 May 2024 18:26:13 -0700 (PDT)	[thread overview]
Message-ID: <6657d5b5.050a0220.9b9d2.4458SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240529225732.442539-9-stephen@networkplumber.org>

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

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, May 29 2024 22:54:45 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:76cef1af8bdaeaf67a5c4ca5df3f221df994dc46

140401-140408 --> functional testing pass

Test environment and result as below:

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  |
+-----------------+--------+


Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: Unknown

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


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  |
+------------+--------+


Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
NIC: Intel Corporation QAT 8970 0 Mbps
Target: Unknown

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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-30  1:26 UTC|newest]

Thread overview: 172+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240529225732.442539-9-stephen@networkplumber.org>
2024-05-29 22:31 ` |SUCCESS| pw140401-140408 [PATCH v6 8/8] test: update to latencystats tests qemudev
2024-05-29 22:36 ` qemudev
2024-05-29 22:59 ` |SUCCESS| pw140408 " checkpatch
2024-05-30  0:03 ` 0-day Robot
2024-05-30  0:25 ` |SUCCESS| pw140401-140408 [PATCH] [v6,8/8] test: update to latencyst dpdklab
2024-05-30  0:29 ` dpdklab
2024-05-30  0:29 ` dpdklab
2024-05-30  0:30 ` dpdklab
2024-05-30  0:31 ` dpdklab
2024-05-30  0:32 ` dpdklab
2024-05-30  0:32 ` dpdklab
2024-05-30  0:32 ` dpdklab
2024-05-30  0:35 ` dpdklab
2024-05-30  0:40 ` dpdklab
2024-05-30  0:48 ` dpdklab
2024-05-30  0:51 ` dpdklab
2024-05-30  0:53 ` dpdklab
2024-05-30  0:54 ` dpdklab
2024-05-30  0:55 ` dpdklab
2024-05-30  0:55 ` dpdklab
2024-05-30  0:55 ` dpdklab
2024-05-30  0:57 ` dpdklab
2024-05-30  0:57 ` dpdklab
2024-05-30  0:58 ` dpdklab
2024-05-30  0:58 ` dpdklab
2024-05-30  0:59 ` dpdklab
2024-05-30  1:00 ` dpdklab
2024-05-30  1:00 ` dpdklab
2024-05-30  1:01 ` dpdklab
2024-05-30  1:02 ` dpdklab
2024-05-30  1:02 ` dpdklab
2024-05-30  1:02 ` dpdklab
2024-05-30  1:03 ` dpdklab
2024-05-30  1:03 ` dpdklab
2024-05-30  1:04 ` dpdklab
2024-05-30  1:04 ` dpdklab
2024-05-30  1:05 ` dpdklab
2024-05-30  1:14 ` dpdklab
2024-05-30  1:25 ` dpdklab
2024-05-30  1:25 ` dpdklab
2024-05-30  1:26 ` dpdklab [this message]
2024-05-30  1:26 ` dpdklab
2024-05-30  1:26 ` dpdklab
2024-05-30  1:27 ` dpdklab
2024-05-30  1:27 ` dpdklab
2024-05-30  1:27 ` dpdklab
2024-05-30  1:28 ` dpdklab
2024-05-30  1:28 ` dpdklab
2024-05-30  1:28 ` dpdklab
2024-05-30  1:29 ` dpdklab
2024-05-30  1:30 ` dpdklab
2024-05-30  1:31 ` dpdklab
2024-05-30  1:33 ` dpdklab
2024-05-30  1:34 ` dpdklab
2024-05-30  1:35 ` dpdklab
2024-05-30  1:36 ` dpdklab
2024-05-30  1:36 ` dpdklab
2024-05-30  1:40 ` dpdklab
2024-05-30  1:40 ` dpdklab
2024-05-30  1:41 ` dpdklab
2024-05-30  1:41 ` dpdklab
2024-05-30  1:42 ` dpdklab
2024-05-30  1:42 ` dpdklab
2024-05-30  1:42 ` dpdklab
2024-05-30  1:42 ` dpdklab
2024-05-30  1:43 ` dpdklab
2024-05-30  1:45 ` dpdklab
2024-05-30  1:45 ` dpdklab
2024-05-30  1:46 ` dpdklab
2024-05-30  1:47 ` dpdklab
2024-05-30  2:09 ` dpdklab
2024-05-30  2:25 ` dpdklab
2024-05-30  2:38 ` dpdklab
2024-05-30  2:38 ` dpdklab
2024-05-30  7:31 ` dpdklab
2024-05-30  7:31 ` dpdklab
2024-05-30  7:39 ` dpdklab
2024-05-30 15:03 ` dpdklab
2024-05-30 15:03 ` dpdklab
2024-05-30 15:14 ` dpdklab
2024-06-01  7:30 ` dpdklab
2024-06-01  7:32 ` dpdklab
2024-06-01  7:33 ` dpdklab
2024-06-01  7:36 ` dpdklab
2024-06-01  7:36 ` dpdklab
2024-06-01  9:15 ` dpdklab
2024-06-01  9:22 ` dpdklab
2024-06-01  9:46 ` dpdklab
2024-06-01  9:53 ` dpdklab
2024-06-01 10:38 ` dpdklab
2024-06-01 10:41 ` dpdklab
2024-06-01 10:41 ` dpdklab
2024-06-01 10:47 ` dpdklab
2024-06-01 10:49 ` dpdklab
2024-06-01 10:50 ` dpdklab
2024-06-01 10:53 ` dpdklab
2024-06-01 10:54 ` dpdklab
2024-06-01 10:54 ` dpdklab
2024-06-01 10:55 ` dpdklab
2024-06-01 10:56 ` dpdklab
2024-06-01 10:59 ` dpdklab
2024-06-01 11:00 ` dpdklab
2024-06-01 12:17 ` dpdklab
2024-06-01 12:45 ` dpdklab
2024-06-01 13:00 ` dpdklab
2024-06-01 13:39 ` dpdklab
2024-06-01 13:40 ` dpdklab
2024-06-01 14:39 ` dpdklab
2024-06-01 15:07 ` dpdklab
2024-06-01 15:09 ` dpdklab
2024-06-01 15:16 ` dpdklab
2024-06-01 15:16 ` dpdklab
2024-06-01 15:21 ` dpdklab
2024-06-01 15:26 ` dpdklab
2024-06-01 15:27 ` dpdklab
2024-06-01 15:28 ` dpdklab
2024-06-01 15:32 ` dpdklab
2024-06-01 15:32 ` dpdklab
2024-06-01 15:33 ` dpdklab
2024-06-01 15:35 ` dpdklab
2024-06-01 15:37 ` dpdklab
2024-06-01 15:45 ` dpdklab
2024-06-01 15:46 ` dpdklab
2024-06-01 15:47 ` dpdklab
2024-06-01 15:47 ` dpdklab
2024-06-01 15:48 ` dpdklab
2024-06-01 15:52 ` dpdklab
2024-06-01 15:54 ` dpdklab
2024-06-01 15:57 ` dpdklab
2024-06-01 15:59 ` dpdklab
2024-06-01 16:30 ` dpdklab
2024-06-01 16:30 ` dpdklab
2024-06-01 16:32 ` dpdklab
2024-06-01 16:33 ` dpdklab
2024-06-01 16:33 ` dpdklab
2024-06-01 16:33 ` dpdklab
2024-06-01 16:33 ` dpdklab
2024-06-01 16:34 ` dpdklab
2024-06-01 16:35 ` dpdklab
2024-06-01 16:38 ` dpdklab
2024-06-01 16:38 ` dpdklab
2024-06-01 16:39 ` dpdklab
2024-06-01 16:44 ` dpdklab
2024-06-01 16:52 ` dpdklab
2024-06-01 16:53 ` dpdklab
2024-06-01 16:53 ` dpdklab
2024-06-01 16:55 ` dpdklab
2024-06-01 16:55 ` dpdklab
2024-06-01 16:58 ` dpdklab
2024-06-01 16:58 ` dpdklab
2024-06-01 16:59 ` dpdklab
2024-06-01 16:59 ` dpdklab
2024-06-01 17:00 ` dpdklab
2024-06-01 17:00 ` dpdklab
2024-06-01 17:01 ` dpdklab
2024-06-01 17:02 ` dpdklab
2024-06-01 17:05 ` dpdklab
2024-06-01 17:06 ` dpdklab
2024-06-01 17:10 ` dpdklab
2024-06-01 17:12 ` dpdklab
2024-06-01 17:13 ` dpdklab
2024-06-01 17:13 ` dpdklab
2024-06-01 17:16 ` dpdklab
2024-06-01 17:18 ` dpdklab
2024-06-01 18:15 ` dpdklab
2024-06-01 18:20 ` dpdklab
2024-06-01 18:39 ` dpdklab
2024-06-01 18:51 ` dpdklab
2024-06-01 18:53 ` dpdklab
2024-06-01 21:34 ` dpdklab
2024-06-01 21:48 ` dpdklab
2024-06-02  2:09 ` 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=6657d5b5.050a0220.9b9d2.4458SMTPIN_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).