From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139447 [PATCH] lib/vhost: add flag for async connection
Date: Wed, 17 Apr 2024 10:30:39 -0700 (PDT) [thread overview]
Message-ID: <6620073f.920a0220.5cc71.3f23SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240417083835.164456-1-udav@mts.ru>
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139447
_Testing PASS_
Submitter: Ushkov Daniil <udav@mts.ru>
Date: Wednesday, April 17 2024 08:41:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:deedfb86a7a6e10064d3cccd593f62072de96e36
139447 --> testing pass
Test environment and result as below:
+-----------------------------+----------------+------------------------------+---------------------------+
| Environment | dpdk_unit_test | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest |
+=============================+================+==============================+===========================+
| CentOS Stream 9 (ARM) | PASS | SKIPPED | SKIPPED |
+-----------------------------+----------------+------------------------------+---------------------------+
| Debian 11 (Buster) (ARM) | PASS | SKIPPED | SKIPPED |
+-----------------------------+----------------+------------------------------+---------------------------+
| Debian 12 (arm) | PASS | PASS | PASS |
+-----------------------------+----------------+------------------------------+---------------------------+
| 32-bit Ubuntu 20.04.4 (ARM) | PASS | SKIPPED | SKIPPED |
+-----------------------------+----------------+------------------------------+---------------------------+
| Fedora 38 (ARM) | PASS | SKIPPED | SKIPPED |
+-----------------------------+----------------+------------------------------+---------------------------+
| Fedora 37 (ARM) | PASS | SKIPPED | SKIPPED |
+-----------------------------+----------------+------------------------------+---------------------------+
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
32-bit Ubuntu 20.04.4 (ARM)
Kernel: 5.4.0-155-generic aarch64
Compiler: gcc 9.4
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29804/
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:[~2024-04-17 17:30 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240417083835.164456-1-udav@mts.ru>
2024-04-17 8:21 ` |SUCCESS| pw139447 [PATCH] lib/vhost: add flag for async connection in client mode qemudev
2024-04-17 8:25 ` qemudev
2024-04-17 8:42 ` |WARNING| " checkpatch
2024-04-17 9:44 ` |SUCCESS| " 0-day Robot
2024-04-17 15:36 ` |SUCCESS| pw139447 [PATCH] lib/vhost: add flag for async connection dpdklab
2024-04-17 15:41 ` dpdklab
2024-04-17 16:06 ` dpdklab
2024-04-17 16:07 ` dpdklab
2024-04-17 16:11 ` dpdklab
2024-04-17 16:11 ` dpdklab
2024-04-17 16:18 ` dpdklab
2024-04-17 16:18 ` dpdklab
2024-04-17 16:23 ` dpdklab
2024-04-17 16:31 ` dpdklab
2024-04-17 16:35 ` dpdklab
2024-04-17 16:35 ` dpdklab
2024-04-17 16:36 ` dpdklab
2024-04-17 16:37 ` dpdklab
2024-04-17 16:37 ` dpdklab
2024-04-17 16:38 ` dpdklab
2024-04-17 16:39 ` dpdklab
2024-04-17 16:40 ` dpdklab
2024-04-17 16:41 ` dpdklab
2024-04-17 16:42 ` dpdklab
2024-04-17 16:44 ` dpdklab
2024-04-17 16:46 ` dpdklab
2024-04-17 16:46 ` dpdklab
2024-04-17 16:48 ` dpdklab
2024-04-17 16:48 ` dpdklab
2024-04-17 16:53 ` dpdklab
2024-04-17 16:58 ` dpdklab
2024-04-17 17:00 ` dpdklab
2024-04-17 17:00 ` dpdklab
2024-04-17 17:01 ` dpdklab
2024-04-17 17:02 ` dpdklab
2024-04-17 17:02 ` dpdklab
2024-04-17 17:09 ` dpdklab
2024-04-17 17:10 ` dpdklab
2024-04-17 17:10 ` dpdklab
2024-04-17 17:11 ` dpdklab
2024-04-17 17:12 ` dpdklab
2024-04-17 17:12 ` dpdklab
2024-04-17 17:13 ` dpdklab
2024-04-17 17:14 ` dpdklab
2024-04-17 17:16 ` dpdklab
2024-04-17 17:19 ` dpdklab
2024-04-17 17:29 ` dpdklab
2024-04-17 17:30 ` dpdklab
2024-04-17 17:30 ` dpdklab [this message]
2024-04-17 17:30 ` dpdklab
2024-04-17 17:32 ` dpdklab
2024-04-17 17:34 ` dpdklab
2024-04-17 17:36 ` dpdklab
2024-04-17 17:36 ` dpdklab
2024-04-17 17:37 ` dpdklab
2024-04-17 17:37 ` dpdklab
2024-04-17 17:37 ` dpdklab
2024-04-17 17:37 ` dpdklab
2024-04-17 17:37 ` dpdklab
2024-04-17 17:38 ` dpdklab
2024-04-17 17:39 ` dpdklab
2024-04-17 17:39 ` dpdklab
2024-04-17 17:41 ` dpdklab
2024-04-17 17:49 ` dpdklab
2024-04-17 17:49 ` dpdklab
2024-04-17 17:58 ` dpdklab
2024-04-17 17:59 ` dpdklab
2024-04-17 18:00 ` dpdklab
2024-04-17 18:01 ` dpdklab
2024-04-17 18:02 ` dpdklab
2024-04-17 18:02 ` dpdklab
2024-04-17 18:03 ` dpdklab
2024-04-17 18:03 ` dpdklab
2024-04-17 18:05 ` dpdklab
2024-04-17 18:06 ` dpdklab
2024-04-17 18:06 ` dpdklab
2024-04-17 18:08 ` dpdklab
2024-04-17 18:11 ` dpdklab
2024-04-17 18:12 ` dpdklab
2024-04-17 18:15 ` dpdklab
2024-04-17 18:18 ` dpdklab
2024-04-17 18:18 ` dpdklab
2024-04-17 18:22 ` dpdklab
2024-04-17 18:23 ` dpdklab
2024-04-17 18:25 ` dpdklab
2024-04-17 18:26 ` dpdklab
2024-04-17 18:28 ` dpdklab
2024-04-17 18:48 ` dpdklab
2024-04-17 18:55 ` dpdklab
2024-04-17 18:55 ` dpdklab
2024-04-17 19:11 ` dpdklab
2024-04-17 19:46 ` dpdklab
2024-04-17 19:47 ` dpdklab
2024-04-26 22:27 ` dpdklab
2024-04-26 22:38 ` dpdklab
2024-04-26 22:42 ` dpdklab
2024-04-26 23:20 ` dpdklab
2024-04-26 23:20 ` dpdklab
2024-04-26 23:21 ` dpdklab
2024-04-26 23:21 ` dpdklab
2024-04-26 23:22 ` dpdklab
2024-04-26 23:22 ` dpdklab
2024-04-26 23:32 ` dpdklab
2024-04-26 23:34 ` dpdklab
2024-04-26 23:34 ` dpdklab
2024-04-26 23:37 ` dpdklab
2024-04-26 23:37 ` dpdklab
2024-04-26 23:41 ` dpdklab
2024-04-26 23:42 ` dpdklab
2024-04-26 23:44 ` 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=6620073f.920a0220.5cc71.3f23SMTPIN_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).