From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw145136-145145 [PATCH] [10/10] ethdev: require checking r
Date: Fri, 04 Oct 2024 21:16:50 -0700 (PDT) [thread overview]
Message-ID: <6700bdb2.170a0220.18be61.22e3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241004162418.52940-11-stephen@networkplumber.org>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/145145
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, October 04 2024 16:21:57
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:0107bd57c612a3b8b6aab6e5ae761bad3a9c2b1e
145136-145145 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#185492
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 |
+=============================+========+
| 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 |
+=============================+========+
| 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/patchsets/31300/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-10-05 4:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241004162418.52940-11-stephen@networkplumber.org>
2024-10-04 16:00 ` |SUCCESS| pw145136-145145 [PATCH 10/10] ethdev: require checking results of info_get functions qemudev
2024-10-04 16:04 ` qemudev
2024-10-04 16:26 ` |SUCCESS| pw145145 " checkpatch
2024-10-04 17:23 ` 0-day Robot
2024-10-05 1:14 ` |PENDING| pw145136-145145 [PATCH] [10/10] ethdev: require checking r dpdklab
2024-10-05 1:20 ` |SUCCESS| " dpdklab
2024-10-05 1:41 ` dpdklab
2024-10-05 1:44 ` dpdklab
2024-10-05 1:46 ` dpdklab
2024-10-05 1:46 ` dpdklab
2024-10-05 2:05 ` |PENDING| " dpdklab
2024-10-05 2:28 ` dpdklab
2024-10-05 2:30 ` |SUCCESS| " dpdklab
2024-10-05 3:45 ` dpdklab
2024-10-05 3:53 ` dpdklab
2024-10-05 4:00 ` dpdklab
2024-10-05 4:09 ` |PENDING| " dpdklab
2024-10-05 4:16 ` dpdklab [this message]
2024-10-05 4:20 ` |SUCCESS| " dpdklab
2024-10-05 6:35 ` dpdklab
2024-10-05 6:40 ` 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=6700bdb2.170a0220.18be61.22e3SMTPIN_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).