From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw157144-157146 [PATCH] [v1,3/3] app/test: add ML crypto t
Date: Tue, 30 Sep 2025 14:59:53 -0700 (PDT) [thread overview]
Message-ID: <68dc52d9.050a0220.11bd40.7247SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250930180316.1021-4-gmuthukrishn@marvell.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/157146
_Functional Testing PASS_
Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Tuesday, September 30 2025 18:03:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f3878b615e69a12087a6c5d212723478cfc79c31
157144-157146 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#247229
Test environment and result as below:
Ubuntu 20.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34185/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-09-30 21:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250930180316.1021-4-gmuthukrishn@marvell.com>
2025-09-30 17:29 ` |SUCCESS| pw157144-157146 [PATCH v1 3/3] app/test: add ML crypto test vectors qemudev
2025-09-30 17:34 ` qemudev
2025-09-30 18:05 ` |WARNING| pw157146 " checkpatch
2025-09-30 18:34 ` |PENDING| pw157144-157146 [PATCH] [v1,3/3] app/test: add ML crypto t dpdklab
2025-09-30 18:37 ` |SUCCESS| " dpdklab
2025-09-30 18:37 ` |PENDING| " dpdklab
2025-09-30 18:37 ` |FAILURE| " dpdklab
2025-09-30 18:38 ` dpdklab
2025-09-30 18:38 ` dpdklab
2025-09-30 18:48 ` dpdklab
2025-09-30 18:49 ` |PENDING| " dpdklab
2025-09-30 18:52 ` |FAILURE| " dpdklab
2025-09-30 18:54 ` dpdklab
2025-09-30 18:54 ` dpdklab
2025-09-30 18:56 ` dpdklab
2025-09-30 18:58 ` |SUCCESS| " dpdklab
2025-09-30 19:00 ` |FAILURE| " dpdklab
2025-09-30 19:00 ` |SUCCESS| " dpdklab
2025-09-30 19:01 ` dpdklab
2025-09-30 19:03 ` |FAILURE| " dpdklab
2025-09-30 19:07 ` dpdklab
2025-09-30 19:08 ` dpdklab
2025-09-30 19:15 ` dpdklab
2025-09-30 19:18 ` dpdklab
2025-09-30 19:28 ` dpdklab
2025-09-30 20:39 ` |FAILURE| pw157146 [PATCH v1 3/3] app/test: add ML crypto test vectors 0-day Robot
2025-09-30 21:59 ` dpdklab [this message]
2025-09-30 22:00 ` |SUCCESS| pw157144-157146 [PATCH] [v1,3/3] app/test: add ML crypto t dpdklab
2025-10-01 1:56 ` |FAILURE| " dpdklab
2025-10-01 2:06 ` dpdklab
2025-10-01 2:20 ` |PENDING| " dpdklab
2025-10-01 2:36 ` |FAILURE| " dpdklab
2025-10-01 2:50 ` dpdklab
2025-10-01 3:44 ` dpdklab
2025-10-01 4:02 ` dpdklab
2025-10-01 4:18 ` dpdklab
2025-10-01 4:45 ` dpdklab
2025-10-01 5:35 ` dpdklab
2025-10-01 9:06 ` dpdklab
2025-10-01 14:11 ` dpdklab
2025-10-01 14:12 ` dpdklab
2025-10-01 15:46 ` 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=68dc52d9.050a0220.11bd40.7247SMTPIN_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).