From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Hao Chen <chenh@yusur.tech>, dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135949 [PATCH] vhost: fix deadlock during software live
Date: Thu, 18 Jan 2024 07:10:48 -0800 (PST) [thread overview]
Message-ID: <65a93f78.810a0220.8fbf2.4cf8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135949
_Testing PASS_
Submitter: Hao Chen <chenh@yusur.tech>
Date: Thursday, January 18 2024 10:33:44
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:289ddcad152ebffa7359e414526707eb3f2c0a4a
135949 --> testing pass
Test environment and result as below:
+--------------------------+---------------------------+----------------+------------------------------+
| Environment | cryptodev_sw_zuc_autotest | dpdk_unit_test | cryptodev_sw_snow3g_autotest |
+==========================+===========================+================+==============================+
| Debian 11 (arm) | PASS | SKIPPED | PASS |
+--------------------------+---------------------------+----------------+------------------------------+
| Debian 11 (Buster) (ARM) | SKIPPED | PASS | SKIPPED |
+--------------------------+---------------------------+----------------+------------------------------+
| CentOS Stream 9 (ARM) | SKIPPED | PASS | SKIPPED |
+--------------------------+---------------------------+----------------+------------------------------+
| Fedora 38 (ARM) | SKIPPED | PASS | SKIPPED |
+--------------------------+---------------------------+----------------+------------------------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28897/
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-18 15:10 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 15:10 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-19 16:18 dpdklab
2024-01-18 21:55 dpdklab
2024-01-18 17:21 dpdklab
2024-01-18 17:15 dpdklab
2024-01-18 17:14 dpdklab
2024-01-18 17:12 dpdklab
2024-01-18 17:11 dpdklab
2024-01-18 17:11 dpdklab
2024-01-18 17:10 dpdklab
2024-01-18 17:10 dpdklab
2024-01-18 17:04 dpdklab
2024-01-18 17:01 dpdklab
2024-01-18 16:59 dpdklab
2024-01-18 16:46 dpdklab
2024-01-18 16:45 dpdklab
2024-01-18 16:44 dpdklab
2024-01-18 16:32 dpdklab
2024-01-18 16:30 dpdklab
2024-01-18 16:19 dpdklab
2024-01-18 16:18 dpdklab
2024-01-18 16:17 dpdklab
2024-01-18 16:17 dpdklab
2024-01-18 16:16 dpdklab
2024-01-18 16:16 dpdklab
2024-01-18 16:16 dpdklab
2024-01-18 16:08 dpdklab
2024-01-18 16:06 dpdklab
2024-01-18 16:05 dpdklab
2024-01-18 16:04 dpdklab
2024-01-18 16:02 dpdklab
2024-01-18 16:02 dpdklab
2024-01-18 16:01 dpdklab
2024-01-18 16:00 dpdklab
2024-01-18 15:59 dpdklab
2024-01-18 15:58 dpdklab
2024-01-18 15:49 dpdklab
2024-01-18 15:49 dpdklab
2024-01-18 15:48 dpdklab
2024-01-18 15:21 dpdklab
2024-01-18 15:15 dpdklab
2024-01-18 15:15 dpdklab
2024-01-18 15:14 dpdklab
2024-01-18 15:14 dpdklab
2024-01-18 15:10 dpdklab
2024-01-18 15:10 dpdklab
2024-01-18 15:10 dpdklab
2024-01-18 15:10 dpdklab
2024-01-18 15:09 dpdklab
2024-01-18 15:09 dpdklab
2024-01-18 15:08 dpdklab
2024-01-18 15:08 dpdklab
2024-01-18 15:08 dpdklab
2024-01-18 15:07 dpdklab
2024-01-18 15:07 dpdklab
2024-01-18 15:06 dpdklab
2024-01-18 15:05 dpdklab
2024-01-18 15:03 dpdklab
2024-01-18 15:03 dpdklab
2024-01-18 15:02 dpdklab
2024-01-18 15:00 dpdklab
2024-01-18 15:00 dpdklab
2024-01-18 14:59 dpdklab
2024-01-18 14:59 dpdklab
2024-01-18 14:58 dpdklab
2024-01-18 14:58 dpdklab
2024-01-18 14:32 dpdklab
2024-01-18 14:29 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=65a93f78.810a0220.8fbf2.4cf8SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=chenh@yusur.tech \
--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).