From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw155542 [PATCH] dts: call hugepages configure at testrun
Date: Mon, 28 Jul 2025 14:11:33 -0700 (PDT) [thread overview]
Message-ID: <6887e785.5d0a0220.103b4c.9536SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250725200553.1262542-1-probb@iol.unh.edu>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/155542
_Functional Testing PASS_
Submitter: Patrick Robb <probb@iol.unh.edu>
Date: Friday, July 25 2025 20:05:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ca046f964fe358dc360c603f79f431beddfcab6
155542 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#238314
Test environment and result as below:
Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: Intel Corporation 4xxx Series QAT 0 Mbps
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | PASS |
+----------------------------+--------+
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Intel Corporation QAT 8970 0 Mbps
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | PASS |
+----------------------------+--------+
Ubuntu 20.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 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 |
+-----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33755/
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:[~2025-07-28 21:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250725200553.1262542-1-probb@iol.unh.edu>
2025-07-25 19:37 ` |SUCCESS| pw155542 [PATCH] dts: call hugepages configure at testrun setup qemudev
2025-07-25 19:42 ` qemudev
2025-07-25 20:11 ` checkpatch
2025-07-25 21:03 ` 0-day Robot
2025-07-28 19:02 ` |SUCCESS| pw155542 [PATCH] dts: call hugepages configure at testrun dpdklab
2025-07-28 19:06 ` dpdklab
2025-07-28 19:17 ` dpdklab
2025-07-28 19:24 ` |PENDING| " dpdklab
2025-07-28 19:27 ` |SUCCESS| " dpdklab
2025-07-28 19:31 ` dpdklab
2025-07-28 19:46 ` dpdklab
2025-07-28 19:46 ` dpdklab
2025-07-28 19:53 ` |PENDING| " dpdklab
2025-07-28 20:00 ` |SUCCESS| " dpdklab
2025-07-28 20:16 ` |PENDING| " dpdklab
2025-07-28 20:31 ` |SUCCESS| " dpdklab
2025-07-28 20:38 ` dpdklab
2025-07-28 20:39 ` dpdklab
2025-07-28 20:51 ` dpdklab
2025-07-28 21:11 ` dpdklab [this message]
2025-07-28 21:59 ` dpdklab
2025-07-28 22:08 ` dpdklab
2025-07-29 0:05 ` dpdklab
2025-07-29 0:30 ` dpdklab
2025-07-29 1:13 ` dpdklab
2025-07-29 3:58 ` dpdklab
2025-07-29 3:58 ` 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=6887e785.5d0a0220.103b4c.9536SMTPIN_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).