From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Stephen Hemminger <stephen@networkplumber.org>
Subject: |SUCCESS| [GIT MASTER] ff05ee3e3f8fb4ce958a2ce6461e8141aea959c6
Date: Tue, 29 Apr 2025 23:55:54 -0700 (PDT) [thread overview]
Message-ID: <6811c97a.050a0220.2f68f4.8a9cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net
ff05ee3e3f8fb4ce958a2ce6461e8141aea959c6 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#223689
Test environment and result as below:
Ubuntu 24.04 LTS
Kernel: 6.8.0-55-generic
Compiler: gcc 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/33397/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-04-30 6:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 6:55 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-30 11:48 dpdklab
2025-04-30 11:17 dpdklab
2025-04-30 10:22 dpdklab
2025-04-30 10:18 dpdklab
2025-04-30 10:09 dpdklab
2025-04-30 7:22 dpdklab
2025-04-30 7:17 dpdklab
2025-04-30 7:10 dpdklab
2025-04-30 7:04 dpdklab
2025-04-30 6:59 dpdklab
2025-04-30 6:56 dpdklab
2025-04-30 6:50 dpdklab
2025-04-30 6:49 dpdklab
2025-04-30 6:43 dpdklab
2025-04-30 6:42 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=6811c97a.050a0220.2f68f4.8a9cSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=stephen@networkplumber.org \
--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).