From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw153444 [PATCH] crypto/virtio: check for invalid IOVA add
Date: Thu, 15 May 2025 09:00:08 -0700 (PDT) [thread overview]
Message-ID: <68260f88.d40a0220.1647da.0458SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250515080313.1612-1-gmuthukrishn@marvell.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/153444
_Functional Testing PASS_
Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Thursday, May 15 2025 08:03:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:dcf9f9363aa9b4163d241caf8b26a84ca0c0006b
153444 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#225939
Test environment and result as below:
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 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/33175/
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-05-15 16:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250515080313.1612-1-gmuthukrishn@marvell.com>
2025-05-15 7:29 ` |SUCCESS| pw153444 [PATCH] crypto/virtio: check for invalid IOVA address qemudev
2025-05-15 7:34 ` qemudev
2025-05-15 8:03 ` checkpatch
2025-05-15 9:03 ` 0-day Robot
2025-05-15 15:45 ` |SUCCESS| pw153444 [PATCH] crypto/virtio: check for invalid IOVA add dpdklab
2025-05-15 15:45 ` dpdklab
2025-05-15 15:55 ` dpdklab
2025-05-15 15:56 ` dpdklab
2025-05-15 15:57 ` dpdklab
2025-05-15 16:00 ` dpdklab [this message]
2025-05-15 16:13 ` dpdklab
2025-05-15 16:19 ` dpdklab
2025-05-15 16:24 ` dpdklab
2025-05-15 16:41 ` |PENDING| " dpdklab
2025-05-15 16:44 ` dpdklab
2025-05-15 16:58 ` dpdklab
2025-05-15 17:08 ` dpdklab
2025-05-15 17:43 ` dpdklab
2025-05-15 18:04 ` |SUCCESS| " dpdklab
2025-05-15 18:14 ` dpdklab
2025-05-15 18:15 ` dpdklab
2025-05-15 18:21 ` dpdklab
2025-05-15 18:27 ` |WARNING| " dpdklab
2025-05-15 19:52 ` |SUCCESS| " dpdklab
2025-05-15 19:57 ` dpdklab
2025-05-15 20:19 ` dpdklab
2025-05-15 20:26 ` dpdklab
2025-05-15 21:06 ` |WARNING| " 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=68260f88.d40a0220.1647da.0458SMTPIN_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).