From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |SUCCESS| [GIT MASTER] 684d996a201182b5335012055df33284e753d832
Date: Fri, 28 Mar 2025 21:47:53 -0700 (PDT) [thread overview]
Message-ID: <67e77b79.920a0220.2f27aa.abd2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: tags/v22.11
684d996a201182b5335012055df33284e753d832 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#219488
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 XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | 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/33093/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-03-29 4:47 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-29 4:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-31 9:16 dpdklab
2025-03-31 6:59 dpdklab
2025-03-31 6:02 dpdklab
2025-03-31 5:36 dpdklab
2025-03-31 5:36 dpdklab
2025-03-31 4:55 dpdklab
2025-03-31 4:51 dpdklab
2025-03-31 4:42 dpdklab
2025-03-31 4:39 dpdklab
2025-03-31 4:36 dpdklab
2025-03-31 4:30 dpdklab
2025-03-31 4:23 dpdklab
2025-03-31 4:21 dpdklab
2025-03-30 7:58 dpdklab
2025-03-30 7:36 dpdklab
2025-03-30 6:51 dpdklab
2025-03-30 6:13 dpdklab
2025-03-30 5:49 dpdklab
2025-03-30 5:37 dpdklab
2025-03-30 5:37 dpdklab
2025-03-30 5:22 dpdklab
2025-03-30 5:06 dpdklab
2025-03-30 5:04 dpdklab
2025-03-30 5:01 dpdklab
2025-03-30 4:38 dpdklab
2025-03-30 4:28 dpdklab
2025-03-29 9:51 dpdklab
2025-03-29 7:38 dpdklab
2025-03-29 7:11 dpdklab
2025-03-29 5:40 dpdklab
2025-03-29 4:59 dpdklab
2025-03-29 4:55 dpdklab
2025-03-29 4:42 dpdklab
2025-03-29 4:42 dpdklab
2025-03-29 4:31 dpdklab
2025-03-29 4:24 dpdklab
2025-03-28 23:14 dpdklab
2025-03-28 21:25 dpdklab
2025-03-28 19:38 dpdklab
2025-03-28 8:33 dpdklab
2025-03-28 8:23 dpdklab
2025-03-28 6:10 dpdklab
2025-03-28 5:45 dpdklab
2025-03-28 5:44 dpdklab
2025-03-28 5:37 dpdklab
2025-03-28 5:17 dpdklab
2025-03-28 5:12 dpdklab
2025-03-28 5:10 dpdklab
2025-03-28 5:03 dpdklab
2025-03-27 7:21 dpdklab
2025-03-27 6:44 dpdklab
2025-03-27 6:09 dpdklab
2025-03-27 6:08 dpdklab
2025-03-27 5:15 dpdklab
2025-03-27 5:11 dpdklab
2025-03-27 4:57 dpdklab
2025-03-27 4:53 dpdklab
2025-03-27 4:40 dpdklab
2025-03-27 4:30 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=67e77b79.920a0220.2f27aa.abd2SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).