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] 3b43ce3f4a54468e7ef65760c2fd7b4d6ee6d9fc
Date: Mon, 22 Sep 2025 21:11:22 -0700 (PDT) [thread overview]
Message-ID: <68d21dea.050a0220.171216.19e3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: tags/v22.11
3b43ce3f4a54468e7ef65760c2fd7b4d6ee6d9fc --> functional testing pass
Upstream job id: Template-DTS-Pipeline#245758
Test environment and result as below:
Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc
Aggregate Results by Test Suite
+----------------+--------+
| Test Suite | Result |
+================+========+
| cmdline | PASS |
+----------------+--------+
| dynamic_queue | PASS |
+----------------+--------+
| rxtx_callbacks | PASS |
+----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/34963/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-09-23 4:11 UTC|newest]
Thread overview: 181+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 4:11 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-03 0:15 dpdklab
2025-10-02 14:06 dpdklab
2025-10-02 5:43 dpdklab
2025-10-02 5:26 dpdklab
2025-10-02 4:32 dpdklab
2025-10-02 4:31 dpdklab
2025-10-02 4:25 dpdklab
2025-10-02 4:16 dpdklab
2025-10-02 2:05 dpdklab
2025-10-01 18:29 dpdklab
2025-10-01 14:19 dpdklab
2025-10-01 6:42 dpdklab
2025-10-01 6:29 dpdklab
2025-10-01 5:45 dpdklab
2025-10-01 5:45 dpdklab
2025-10-01 5:07 dpdklab
2025-10-01 5:06 dpdklab
2025-10-01 4:56 dpdklab
2025-10-01 4:53 dpdklab
2025-10-01 4:47 dpdklab
2025-10-01 4:47 dpdklab
2025-10-01 4:40 dpdklab
2025-09-30 17:36 dpdklab
2025-09-30 17:04 dpdklab
2025-09-30 6:28 dpdklab
2025-09-30 5:29 dpdklab
2025-09-30 5:24 dpdklab
2025-09-30 5:24 dpdklab
2025-09-30 4:42 dpdklab
2025-09-30 4:35 dpdklab
2025-09-30 4:31 dpdklab
2025-09-30 4:20 dpdklab
2025-09-30 4:19 dpdklab
2025-09-30 4:17 dpdklab
2025-09-29 7:11 dpdklab
2025-09-29 7:06 dpdklab
2025-09-29 6:49 dpdklab
2025-09-29 6:11 dpdklab
2025-09-29 6:09 dpdklab
2025-09-29 6:08 dpdklab
2025-09-29 5:52 dpdklab
2025-09-29 5:52 dpdklab
2025-09-29 5:19 dpdklab
2025-09-29 4:52 dpdklab
2025-09-29 4:46 dpdklab
2025-09-29 4:42 dpdklab
2025-09-28 5:38 dpdklab
2025-09-28 5:29 dpdklab
2025-09-28 5:24 dpdklab
2025-09-28 5:24 dpdklab
2025-09-28 5:14 dpdklab
2025-09-28 4:45 dpdklab
2025-09-28 4:29 dpdklab
2025-09-28 4:28 dpdklab
2025-09-28 4:20 dpdklab
2025-09-28 4:17 dpdklab
2025-09-28 4:16 dpdklab
2025-09-27 12:12 dpdklab
2025-09-27 5:58 dpdklab
2025-09-27 5:38 dpdklab
2025-09-27 5:34 dpdklab
2025-09-27 5:27 dpdklab
2025-09-27 5:24 dpdklab
2025-09-27 5:24 dpdklab
2025-09-27 5:19 dpdklab
2025-09-27 5:19 dpdklab
2025-09-27 5:19 dpdklab
2025-09-27 5:18 dpdklab
2025-09-27 4:49 dpdklab
2025-09-27 4:34 dpdklab
2025-09-27 4:31 dpdklab
2025-09-27 0:37 dpdklab
2025-09-26 22:08 dpdklab
2025-09-26 7:15 dpdklab
2025-09-26 5:46 dpdklab
2025-09-26 5:36 dpdklab
2025-09-26 5:36 dpdklab
2025-09-26 5:36 dpdklab
2025-09-26 5:36 dpdklab
2025-09-26 5:36 dpdklab
2025-09-26 5:35 dpdklab
2025-09-26 5:24 dpdklab
2025-09-26 5:17 dpdklab
2025-09-26 4:23 dpdklab
2025-09-26 4:22 dpdklab
2025-09-25 18:04 dpdklab
2025-09-25 8:58 dpdklab
2025-09-25 6:17 dpdklab
2025-09-25 5:53 dpdklab
2025-09-25 5:39 dpdklab
2025-09-25 5:24 dpdklab
2025-09-25 5:24 dpdklab
2025-09-25 5:16 dpdklab
2025-09-25 4:46 dpdklab
2025-09-25 4:21 dpdklab
2025-09-25 4:17 dpdklab
2025-09-25 4:16 dpdklab
2025-09-24 7:06 dpdklab
2025-09-24 5:33 dpdklab
2025-09-24 5:24 dpdklab
2025-09-24 5:23 dpdklab
2025-09-24 5:11 dpdklab
2025-09-24 4:58 dpdklab
2025-09-24 4:29 dpdklab
2025-09-24 4:28 dpdklab
2025-09-24 4:20 dpdklab
2025-09-24 4:17 dpdklab
2025-09-23 7:02 dpdklab
2025-09-23 5:56 dpdklab
2025-09-23 5:52 dpdklab
2025-09-23 5:51 dpdklab
2025-09-23 5:37 dpdklab
2025-09-23 5:33 dpdklab
2025-09-23 5:25 dpdklab
2025-09-23 4:46 dpdklab
2025-09-23 4:43 dpdklab
2025-09-23 4:31 dpdklab
2025-09-23 4:29 dpdklab
2025-09-23 4:19 dpdklab
2025-09-22 6:53 dpdklab
2025-09-22 6:15 dpdklab
2025-09-22 5:29 dpdklab
2025-09-22 5:24 dpdklab
2025-09-22 5:24 dpdklab
2025-09-22 5:24 dpdklab
2025-09-22 5:08 dpdklab
2025-09-22 4:42 dpdklab
2025-09-22 4:28 dpdklab
2025-09-22 4:20 dpdklab
2025-09-22 4:17 dpdklab
2025-09-21 7:15 dpdklab
2025-09-21 5:57 dpdklab
2025-09-21 5:49 dpdklab
2025-09-21 5:38 dpdklab
2025-09-21 5:28 dpdklab
2025-09-21 5:24 dpdklab
2025-09-21 5:24 dpdklab
2025-09-21 5:08 dpdklab
2025-09-21 5:07 dpdklab
2025-09-21 4:53 dpdklab
2025-09-21 4:37 dpdklab
2025-09-21 4:31 dpdklab
2025-09-21 4:29 dpdklab
2025-09-20 10:02 dpdklab
2025-09-20 7:59 dpdklab
2025-09-20 6:08 dpdklab
2025-09-20 5:32 dpdklab
2025-09-20 5:30 dpdklab
2025-09-20 5:24 dpdklab
2025-09-20 5:24 dpdklab
2025-09-20 4:45 dpdklab
2025-09-20 4:29 dpdklab
2025-09-20 4:28 dpdklab
2025-09-20 4:20 dpdklab
2025-09-20 4:17 dpdklab
2025-09-20 4:16 dpdklab
2025-09-19 16:45 dpdklab
2025-09-19 8:36 dpdklab
2025-09-19 5:32 dpdklab
2025-09-19 5:24 dpdklab
2025-09-19 5:12 dpdklab
2025-09-19 5:03 dpdklab
2025-09-19 4:52 dpdklab
2025-09-19 4:29 dpdklab
2025-09-19 4:28 dpdklab
2025-09-19 4:20 dpdklab
2025-09-19 4:11 dpdklab
2025-09-18 19:10 dpdklab
2025-09-18 10:47 dpdklab
2025-09-18 10:00 dpdklab
2025-09-18 6:02 dpdklab
2025-09-18 5:33 dpdklab
2025-09-18 5:27 dpdklab
2025-09-18 5:24 dpdklab
2025-09-18 5:24 dpdklab
2025-09-18 4:55 dpdklab
2025-09-18 4:29 dpdklab
2025-09-18 4:21 dpdklab
2025-09-18 4:17 dpdklab
2025-09-18 4: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=68d21dea.050a0220.171216.19e3SMTPIN_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).