From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 38543d33bd47fc0ee21f59db80a8763620741879
Date: Wed, 13 Aug 2025 17:31:42 -0700 (PDT) [thread overview]
Message-ID: <689d2e6e.170a0220.e40fc.eac2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk
38543d33bd47fc0ee21f59db80a8763620741879 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#240242
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 |
+----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/34570/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-08-14 0:31 UTC|newest]
Thread overview: 123+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 0:31 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-20 4:07 dpdklab
2025-08-20 1:08 dpdklab
2025-08-20 1:01 dpdklab
2025-08-20 0:58 dpdklab
2025-08-20 0:51 dpdklab
2025-08-20 0:45 dpdklab
2025-08-20 0:43 dpdklab
2025-08-20 0:43 dpdklab
2025-08-20 0:41 dpdklab
2025-08-20 0:38 dpdklab
2025-08-20 0:30 dpdklab
2025-08-20 0:29 dpdklab
2025-08-16 4:10 dpdklab
2025-08-16 4:03 dpdklab
2025-08-16 1:56 dpdklab
2025-08-16 1:15 dpdklab
2025-08-16 1:01 dpdklab
2025-08-16 1:01 dpdklab
2025-08-16 0:54 dpdklab
2025-08-16 0:51 dpdklab
2025-08-16 0:48 dpdklab
2025-08-16 0:44 dpdklab
2025-08-16 0:43 dpdklab
2025-08-16 0:41 dpdklab
2025-08-16 0:31 dpdklab
2025-08-14 13:51 dpdklab
2025-08-14 3:36 dpdklab
2025-08-14 1:58 dpdklab
2025-08-14 1:12 dpdklab
2025-08-14 1:02 dpdklab
2025-08-14 1:00 dpdklab
2025-08-14 0:53 dpdklab
2025-08-14 0:52 dpdklab
2025-08-14 0:50 dpdklab
2025-08-14 0:45 dpdklab
2025-08-14 0:44 dpdklab
2025-08-14 0:44 dpdklab
2025-08-14 0:44 dpdklab
2025-08-14 0:30 dpdklab
2025-08-11 16:58 dpdklab
2025-08-11 8:19 dpdklab
2025-08-10 3:44 dpdklab
2025-08-10 1:29 dpdklab
2025-08-10 1:16 dpdklab
2025-08-10 1:04 dpdklab
2025-08-10 1:03 dpdklab
2025-08-10 0:48 dpdklab
2025-08-10 0:42 dpdklab
2025-08-10 0:42 dpdklab
2025-08-10 0:41 dpdklab
2025-08-10 0:30 dpdklab
2025-08-08 7:48 dpdklab
2025-08-08 3:33 dpdklab
2025-08-08 3:31 dpdklab
2025-08-08 1:22 dpdklab
2025-08-08 1:03 dpdklab
2025-08-08 0:51 dpdklab
2025-08-08 0:50 dpdklab
2025-08-08 0:48 dpdklab
2025-08-08 0:47 dpdklab
2025-08-08 0:44 dpdklab
2025-08-08 0:25 dpdklab
2025-08-08 0:24 dpdklab
2025-08-06 14:41 dpdklab
2025-08-06 3:36 dpdklab
2025-08-06 1:26 dpdklab
2025-08-06 1:14 dpdklab
2025-08-06 1:06 dpdklab
2025-08-06 1:02 dpdklab
2025-08-06 0:59 dpdklab
2025-08-06 0:58 dpdklab
2025-08-06 0:39 dpdklab
2025-08-06 0:38 dpdklab
2025-08-06 0:29 dpdklab
2025-08-06 0:27 dpdklab
2025-08-06 0:23 dpdklab
2025-08-04 1:53 dpdklab
2025-08-04 1:44 dpdklab
2025-08-04 1:32 dpdklab
2025-08-04 1:27 dpdklab
2025-08-04 0:32 dpdklab
2025-08-04 0:31 dpdklab
2025-08-02 3:48 dpdklab
2025-08-02 1:32 dpdklab
2025-08-02 1:14 dpdklab
2025-08-02 1:01 dpdklab
2025-08-02 0:58 dpdklab
2025-08-02 0:57 dpdklab
2025-08-02 0:53 dpdklab
2025-08-02 0:49 dpdklab
2025-08-02 0:49 dpdklab
2025-08-02 0:46 dpdklab
2025-08-02 0:45 dpdklab
2025-08-02 0:45 dpdklab
2025-08-02 0:31 dpdklab
2025-08-02 0:30 dpdklab
2025-08-01 3:39 dpdklab
2025-08-01 1:19 dpdklab
2025-08-01 1:05 dpdklab
2025-08-01 1:03 dpdklab
2025-08-01 0:55 dpdklab
2025-08-01 0:54 dpdklab
2025-08-01 0:53 dpdklab
2025-08-01 0:49 dpdklab
2025-08-01 0:46 dpdklab
2025-08-01 0:45 dpdklab
2025-08-01 0:41 dpdklab
2025-08-01 0:31 dpdklab
2025-08-01 0:28 dpdklab
2025-07-30 4:01 dpdklab
2025-07-30 2:17 dpdklab
2025-07-30 1:17 dpdklab
2025-07-30 1:17 dpdklab
2025-07-30 0:58 dpdklab
2025-07-30 0:57 dpdklab
2025-07-30 0:57 dpdklab
2025-07-30 0:50 dpdklab
2025-07-30 0:42 dpdklab
2025-07-30 0:41 dpdklab
2025-07-30 0:39 dpdklab
2025-07-30 0:31 dpdklab
2025-07-30 0:28 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=689d2e6e.170a0220.e40fc.eac2SMTPIN_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).