From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 7df61db6c387703a36306c1aea92225921e2eeb2
Date: Wed, 04 Dec 2024 11:51:09 -0800 (PST) [thread overview]
Message-ID: <6750b2ad.170a0220.109a6a.6449SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk
7df61db6c387703a36306c1aea92225921e2eeb2 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#201070
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 |
+-----------------------------+--------+
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 |
+=============================+========+
| 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/31843/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-12-04 19:51 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 19:51 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-10 3:31 dpdklab
2024-12-10 2:09 dpdklab
2024-12-10 2:06 dpdklab
2024-12-10 1:54 dpdklab
2024-12-10 1:50 dpdklab
2024-12-10 1:49 dpdklab
2024-12-10 1:44 dpdklab
2024-12-10 1:42 dpdklab
2024-12-10 1:40 dpdklab
2024-12-10 1:40 dpdklab
2024-12-10 1:32 dpdklab
2024-12-10 1:29 dpdklab
2024-12-10 1:23 dpdklab
2024-12-08 3:22 dpdklab
2024-12-08 2:08 dpdklab
2024-12-08 2:05 dpdklab
2024-12-08 1:49 dpdklab
2024-12-08 1:48 dpdklab
2024-12-08 1:47 dpdklab
2024-12-08 1:43 dpdklab
2024-12-08 1:40 dpdklab
2024-12-08 1:39 dpdklab
2024-12-08 1:31 dpdklab
2024-12-08 1:30 dpdklab
2024-12-08 1:23 dpdklab
2024-12-06 4:23 dpdklab
2024-12-06 2:02 dpdklab
2024-12-06 2:00 dpdklab
2024-12-06 1:59 dpdklab
2024-12-06 1:50 dpdklab
2024-12-06 1:48 dpdklab
2024-12-06 1:45 dpdklab
2024-12-06 1:43 dpdklab
2024-12-06 1:40 dpdklab
2024-12-06 1:39 dpdklab
2024-12-06 1:32 dpdklab
2024-12-06 1:31 dpdklab
2024-12-06 0:33 dpdklab
2024-12-05 22:27 dpdklab
2024-12-05 21:56 dpdklab
2024-12-05 21:44 dpdklab
2024-12-05 21:37 dpdklab
2024-12-05 21:35 dpdklab
2024-12-05 21:33 dpdklab
2024-12-05 21:30 dpdklab
2024-12-05 21:29 dpdklab
2024-12-05 21:26 dpdklab
2024-12-05 21:25 dpdklab
2024-12-05 21:17 dpdklab
2024-12-05 21:09 dpdklab
2024-12-05 21:09 dpdklab
2024-12-04 21:19 dpdklab
2024-12-04 20:05 dpdklab
2024-12-04 20:03 dpdklab
2024-12-04 19:57 dpdklab
2024-12-04 19:42 dpdklab
2024-12-04 19:34 dpdklab
2024-12-04 19:34 dpdklab
2024-12-04 19:31 dpdklab
2024-12-04 19:30 dpdklab
2024-12-04 19:22 dpdklab
2024-12-04 19:17 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=6750b2ad.170a0220.109a6a.6449SMTPIN_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).