From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw153863 [PATCH] [v1,1/1] vhost: handle virtqueue locking
Date: Fri, 30 May 2025 17:22:39 -0700 (PDT) [thread overview]
Message-ID: <683a4bcf.d40a0220.1a7172.bf07SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250529123102.1875027-2-dvo-plv@napatech.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/153863
_Testing PASS_
Submitter: Danylo Vodopianov <dvo-plv@napatech.com>
Date: Thursday, May 29 2025 12:31:02
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3223019e73391066cbb0d248051b163e5373034c
153863 --> testing pass
Upstream job id: ACVP-FIPS-testing#9975
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33279/
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-31 0:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250529123102.1875027-2-dvo-plv@napatech.com>
2025-05-29 12:13 ` |SUCCESS| pw153863 [PATCH v1 1/1] vhost: handle virtqueue locking for memory hotplug qemudev
2025-05-29 12:18 ` qemudev
2025-05-29 12:32 ` |WARNING| " checkpatch
2025-05-29 13:43 ` |SUCCESS| " 0-day Robot
2025-05-29 23:34 ` |SUCCESS| pw153863 [PATCH] [v1,1/1] vhost: handle virtqueue locking dpdklab
2025-05-29 23:45 ` dpdklab
2025-05-30 1:46 ` |PENDING| " dpdklab
2025-05-30 1:54 ` dpdklab
2025-05-30 2:11 ` |SUCCESS| " dpdklab
2025-05-30 2:12 ` dpdklab
2025-05-30 2:12 ` dpdklab
2025-05-30 2:13 ` dpdklab
2025-05-30 2:14 ` dpdklab
2025-05-30 2:14 ` dpdklab
2025-05-30 2:15 ` dpdklab
2025-05-30 2:15 ` dpdklab
2025-05-30 2:40 ` |PENDING| " dpdklab
2025-05-30 4:44 ` |WARNING| " dpdklab
2025-05-30 4:49 ` dpdklab
2025-05-30 4:50 ` dpdklab
2025-05-30 6:08 ` |SUCCESS| " dpdklab
2025-05-30 10:32 ` dpdklab
2025-05-30 11:48 ` |WARNING| " dpdklab
2025-05-30 22:08 ` dpdklab
2025-05-30 22:09 ` dpdklab
2025-05-31 0:22 ` dpdklab [this message]
2025-05-31 3:01 ` |SUCCESS| " dpdklab
2025-05-31 3:03 ` dpdklab
2025-06-04 13:45 ` 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=683a4bcf.d40a0220.1a7172.bf07SMTPIN_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).