From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136017 [PATCH] [v2] vhost: fix deadlock during software
Date: Sun, 21 Jan 2024 20:48:12 -0800 (PST) [thread overview]
Message-ID: <65adf38c.170a0220.0532.3b05SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136017
_Testing PASS_
Submitter: Hao Chen <chenh@yusur.tech>
Date: Monday, January 22 2024 03:27:44
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:289ddcad152ebffa7359e414526707eb3f2c0a4a
136017 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28927/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-22 4:48 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 4:48 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-22 23:54 dpdklab
2024-01-22 23:47 dpdklab
2024-01-22 6:49 dpdklab
2024-01-22 5:48 dpdklab
2024-01-22 5:48 dpdklab
2024-01-22 5:35 dpdklab
2024-01-22 5:35 dpdklab
2024-01-22 5:16 dpdklab
2024-01-22 5:16 dpdklab
2024-01-22 5:15 dpdklab
2024-01-22 5:15 dpdklab
2024-01-22 5:14 dpdklab
2024-01-22 5:14 dpdklab
2024-01-22 5:13 dpdklab
2024-01-22 5:13 dpdklab
2024-01-22 5:00 dpdklab
2024-01-22 4:54 dpdklab
2024-01-22 4:52 dpdklab
2024-01-22 4:52 dpdklab
2024-01-22 4:48 dpdklab
2024-01-22 4:45 dpdklab
2024-01-22 4:44 dpdklab
2024-01-22 4:43 dpdklab
2024-01-22 4:42 dpdklab
2024-01-22 4:41 dpdklab
2024-01-22 4:41 dpdklab
2024-01-22 4:40 dpdklab
2024-01-22 4:40 dpdklab
2024-01-22 4:39 dpdklab
2024-01-22 4:39 dpdklab
2024-01-22 4:38 dpdklab
2024-01-22 4:38 dpdklab
2024-01-22 4:37 dpdklab
2024-01-22 4:37 dpdklab
2024-01-22 4:35 dpdklab
2024-01-22 4:31 dpdklab
2024-01-22 4:29 dpdklab
2024-01-22 4:29 dpdklab
2024-01-22 4:28 dpdklab
2024-01-22 4:27 dpdklab
2024-01-22 4:22 dpdklab
2024-01-22 4:22 dpdklab
2024-01-22 4:22 dpdklab
2024-01-22 4:22 dpdklab
2024-01-22 4:22 dpdklab
2024-01-22 4:20 dpdklab
2024-01-22 4:19 dpdklab
2024-01-22 4:19 dpdklab
2024-01-22 4:18 dpdklab
2024-01-22 4:17 dpdklab
2024-01-22 4:17 dpdklab
2024-01-22 4:17 dpdklab
2024-01-22 4:16 dpdklab
2024-01-22 4:15 dpdklab
2024-01-22 4:14 dpdklab
2024-01-22 4:14 dpdklab
2024-01-22 4:12 dpdklab
2024-01-22 4:12 dpdklab
2024-01-22 4:11 dpdklab
2024-01-22 4:11 dpdklab
2024-01-22 4:11 dpdklab
2024-01-22 4:11 dpdklab
2024-01-22 4:11 dpdklab
2024-01-22 4:11 dpdklab
2024-01-22 4:10 dpdklab
2024-01-22 4:10 dpdklab
2024-01-22 4:10 dpdklab
2024-01-22 4:09 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=65adf38c.170a0220.0532.3b05SMTPIN_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).