From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 07604f264417959d76aa9fcb8cb0c3665f62f0d3
Date: Sat, 21 Dec 2024 17:31:32 -0800 (PST) [thread overview]
Message-ID: <67676bf4.050a0220.295130.db76SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk
07604f264417959d76aa9fcb8cb0c3665f62f0d3 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#203745
Test environment and result as below:
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/tarballs/32011/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-12-22 1:31 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 1:31 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-22 3:35 dpdklab
2024-12-22 2:21 dpdklab
2024-12-22 2:05 dpdklab
2024-12-22 1:58 dpdklab
2024-12-22 1:46 dpdklab
2024-12-22 1:45 dpdklab
2024-12-22 1:44 dpdklab
2024-12-22 1:40 dpdklab
2024-12-22 1:39 dpdklab
2024-12-22 1:38 dpdklab
2024-12-21 10:56 dpdklab
2024-12-21 9:29 dpdklab
2024-12-21 9:18 dpdklab
2024-12-21 9:12 dpdklab
2024-12-21 9:12 dpdklab
2024-12-21 8:51 dpdklab
2024-12-21 8:46 dpdklab
2024-12-21 8:27 dpdklab
2024-12-21 7:56 dpdklab
2024-12-21 7:53 dpdklab
2024-12-21 7:51 dpdklab
2024-12-21 7:51 dpdklab
2024-12-21 7:50 dpdklab
2024-12-21 7:45 dpdklab
2024-12-20 4:28 dpdklab
2024-12-20 3:46 dpdklab
2024-12-20 3:24 dpdklab
2024-12-20 3:04 dpdklab
2024-12-20 2:56 dpdklab
2024-12-20 2:49 dpdklab
2024-12-20 2:32 dpdklab
2024-12-20 2:19 dpdklab
2024-12-20 2:10 dpdklab
2024-12-20 2:05 dpdklab
2024-12-20 2:02 dpdklab
2024-12-20 1:59 dpdklab
2024-12-20 1:52 dpdklab
2024-12-20 1:51 dpdklab
2024-12-19 3:19 dpdklab
2024-12-19 1:47 dpdklab
2024-12-19 0:06 dpdklab
2024-12-18 23:40 dpdklab
2024-12-18 23:36 dpdklab
2024-12-18 23:22 dpdklab
2024-12-18 23:18 dpdklab
2024-12-18 23:17 dpdklab
2024-12-18 23:12 dpdklab
2024-12-18 23:04 dpdklab
2024-12-18 23:00 dpdklab
2024-12-18 22:58 dpdklab
2024-12-18 22:58 dpdklab
2024-12-18 22:54 dpdklab
2024-12-18 22:50 dpdklab
2024-12-18 22:49 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=67676bf4.050a0220.295130.db76SMTPIN_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).