From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw151974-151976 [PATCH] [v5,3/3] app/test: add SM4 GCM tes
Date: Tue, 25 Feb 2025 15:27:59 -0800 (PST) [thread overview]
Message-ID: <67be51ff.050a0220.127430.95ceSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250224165939.717714-3-brian.dooley@intel.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/151976
_Functional Testing PASS_
Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Monday, February 24 2025 16:59:39
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fab31a03ba98e7457284df95dd9eef2223a4ccaa
151974-151976 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#214255
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 |
+----------------+--------+
| rxtx_callbacks | PASS |
+----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32670/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2025-02-25 23:28 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250224165939.717714-3-brian.dooley@intel.com>
2025-02-24 16:25 ` |SUCCESS| pw151974-151976 [PATCH v5 3/3] app/test: add SM4 GCM tests qemudev
2025-02-24 16:29 ` qemudev
2025-02-24 17:00 ` |SUCCESS| pw151976 " checkpatch
2025-02-24 19:24 ` 0-day Robot
2025-02-24 20:52 ` |SUCCESS| pw151974-151976 [PATCH] [v5,3/3] app/test: add SM4 GCM tes dpdklab
2025-02-24 20:54 ` dpdklab
2025-02-24 21:01 ` dpdklab
2025-02-24 21:16 ` dpdklab
2025-02-24 21:19 ` dpdklab
2025-02-24 21:20 ` dpdklab
2025-02-24 21:22 ` dpdklab
2025-02-24 21:26 ` dpdklab
2025-02-24 21:32 ` dpdklab
2025-02-24 21:44 ` dpdklab
2025-02-24 21:54 ` |PENDING| " dpdklab
2025-02-24 22:09 ` dpdklab
2025-02-24 22:17 ` dpdklab
2025-02-24 22:21 ` |SUCCESS| " dpdklab
2025-02-24 22:26 ` |PENDING| " dpdklab
2025-02-24 23:02 ` |SUCCESS| " dpdklab
2025-02-24 23:03 ` dpdklab
2025-02-24 23:03 ` dpdklab
2025-02-24 23:04 ` dpdklab
2025-02-24 23:52 ` dpdklab
2025-02-25 0:09 ` dpdklab
2025-02-25 0:29 ` dpdklab
2025-02-25 0:52 ` dpdklab
2025-02-25 1:14 ` dpdklab
2025-02-25 1:27 ` dpdklab
2025-02-25 1:29 ` dpdklab
2025-02-25 1:30 ` dpdklab
2025-02-25 1:40 ` dpdklab
2025-02-25 1:40 ` dpdklab
2025-02-25 1:49 ` |PENDING| " dpdklab
2025-02-25 1:55 ` |SUCCESS| " dpdklab
2025-02-25 2:11 ` dpdklab
2025-02-25 2:52 ` |PENDING| " dpdklab
2025-02-25 3:02 ` dpdklab
2025-02-25 3:04 ` |SUCCESS| " dpdklab
2025-02-25 3:06 ` |PENDING| " dpdklab
2025-02-25 3:30 ` |SUCCESS| " dpdklab
2025-02-25 3:30 ` dpdklab
2025-02-25 4:17 ` dpdklab
2025-02-25 4:19 ` dpdklab
2025-02-25 4:21 ` dpdklab
2025-02-25 8:34 ` dpdklab
2025-02-25 22:58 ` dpdklab
2025-02-25 23:03 ` dpdklab
2025-02-25 23:27 ` dpdklab [this message]
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=67be51ff.050a0220.127430.95ceSMTPIN_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).