From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
Date: Mon, 16 Sep 2024 17:31:45 -0700 (PDT) [thread overview]
Message-ID: <66e8cdf1.170a0220.c67e5.c799SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk
41dd9a6bc2d9c6e20e139ad713cc9d172572dd43 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#180926
Test environment and result as below:
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
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
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| scatter | PASS |
+-----------------------------+--------+
| unit_tests_mbuf | 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
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
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | PASS |
+----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30506/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-09-17 0:31 UTC|newest]
Thread overview: 128+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 0:31 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-18 18:54 dpdklab
2024-09-18 13:46 dpdklab
2024-09-18 13:13 dpdklab
2024-09-18 10:53 dpdklab
2024-09-18 7:58 dpdklab
2024-09-18 7:53 dpdklab
2024-09-18 7:21 dpdklab
2024-09-18 6:54 dpdklab
2024-09-18 5:57 dpdklab
2024-09-18 5:43 dpdklab
2024-09-18 3:34 dpdklab
2024-09-18 2:54 dpdklab
2024-09-18 2:37 dpdklab
2024-09-18 1:45 dpdklab
2024-09-18 1:45 dpdklab
2024-09-18 1:21 dpdklab
2024-09-17 15:19 dpdklab
2024-09-17 15:01 dpdklab
2024-09-17 10:29 dpdklab
2024-09-17 0:50 dpdklab
2024-09-16 11:48 dpdklab
2024-09-16 5:31 dpdklab
2024-09-16 2:28 dpdklab
2024-09-16 2:25 dpdklab
2024-09-16 2:08 dpdklab
2024-09-16 1:58 dpdklab
2024-09-16 0:52 dpdklab
2024-09-16 0:29 dpdklab
2024-09-16 0:29 dpdklab
2024-09-15 15:34 dpdklab
2024-09-15 11:02 dpdklab
2024-09-15 2:20 dpdklab
2024-09-14 23:15 dpdklab
2024-09-14 20:08 dpdklab
2024-09-14 19:49 dpdklab
2024-09-14 4:17 dpdklab
2024-09-14 2:17 dpdklab
2024-09-14 2:11 dpdklab
2024-09-14 2:09 dpdklab
2024-09-14 2:08 dpdklab
2024-09-14 1:15 dpdklab
2024-09-14 1:01 dpdklab
2024-09-14 0:50 dpdklab
2024-09-14 0:40 dpdklab
2024-09-12 19:27 dpdklab
2024-09-12 10:02 dpdklab
2024-09-12 9:53 dpdklab
2024-09-12 9:49 dpdklab
2024-09-12 9:44 dpdklab
2024-09-12 9:28 dpdklab
2024-09-12 9:24 dpdklab
2024-09-12 9:20 dpdklab
2024-09-12 9:12 dpdklab
2024-09-12 9:07 dpdklab
2024-09-12 4:37 dpdklab
2024-09-12 1:39 dpdklab
2024-09-12 1:01 dpdklab
2024-09-12 0:54 dpdklab
2024-09-10 17:16 dpdklab
2024-09-10 14:30 dpdklab
2024-09-10 13:08 dpdklab
2024-09-10 12:49 dpdklab
2024-09-10 12:45 dpdklab
2024-09-10 12:16 dpdklab
2024-09-10 9:51 dpdklab
2024-09-10 9:50 dpdklab
2024-09-10 9:24 dpdklab
2024-09-10 9:10 dpdklab
2024-09-10 9:10 dpdklab
2024-09-10 9:07 dpdklab
2024-09-10 8:41 dpdklab
2024-09-10 5:17 dpdklab
2024-09-10 5:07 dpdklab
2024-09-10 5:06 dpdklab
2024-09-10 3:40 dpdklab
2024-09-10 2:51 dpdklab
2024-09-10 2:28 dpdklab
2024-09-08 12:29 dpdklab
2024-09-08 3:38 dpdklab
2024-09-08 1:45 dpdklab
2024-09-08 1:41 dpdklab
2024-09-08 1:33 dpdklab
2024-09-08 1:18 dpdklab
2024-09-08 1:13 dpdklab
2024-09-08 1:08 dpdklab
2024-09-08 1:01 dpdklab
2024-09-08 0:44 dpdklab
2024-09-08 0:42 dpdklab
2024-09-08 0:40 dpdklab
2024-09-08 0:30 dpdklab
2024-09-08 0:28 dpdklab
2024-09-08 0:26 dpdklab
2024-09-07 20:48 dpdklab
2024-09-06 21:50 dpdklab
2024-09-06 21:35 dpdklab
2024-09-06 21:32 dpdklab
2024-09-06 19:13 dpdklab
2024-09-06 15:03 dpdklab
2024-09-06 11:07 dpdklab
2024-09-06 11:06 dpdklab
2024-09-06 11:06 dpdklab
2024-09-06 11:05 dpdklab
2024-09-06 11:03 dpdklab
2024-09-06 11:03 dpdklab
2024-09-06 11:02 dpdklab
2024-09-06 11:01 dpdklab
2024-09-06 11:00 dpdklab
2024-09-06 11:00 dpdklab
2024-09-06 10:59 dpdklab
2024-09-06 10:57 dpdklab
2024-09-06 10:57 dpdklab
2024-09-06 10:56 dpdklab
2024-09-06 10:51 dpdklab
2024-09-04 3:01 dpdklab
2024-09-04 1:53 dpdklab
2024-09-04 1:51 dpdklab
2024-09-04 1:43 dpdklab
2024-09-04 1:42 dpdklab
2024-09-04 1:38 dpdklab
2024-09-04 1:34 dpdklab
2024-09-04 1:30 dpdklab
2024-09-04 1:30 dpdklab
2024-09-04 1:29 dpdklab
2024-09-04 1:29 dpdklab
2024-09-04 1:28 dpdklab
2024-09-04 1:27 dpdklab
2024-09-04 1: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=66e8cdf1.170a0220.c67e5.c799SMTPIN_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).