From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Nithin Dabilpuram <ndabilpuram@marvell.com>
Subject: |SUCCESS| pw136918 [PATCH] net/virtio-user: add VIRTIO_F_ORDER_PLATF
Date: Tue, 20 Feb 2024 08:39:24 -0800 (PST) [thread overview]
Message-ID: <65d4d5bc.170a0220.5163c.640cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136918
_Testing PASS_
Submitter: Nithin Dabilpuram <ndabilpuram@marvell.com>
Date: Tuesday, February 20 2024 11:40:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2176806a4052a28bce70fe1767d8a56c6d7e904e
136918 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29192/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-20 16:39 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 16:39 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-21 5:54 dpdklab
2024-02-21 5:40 dpdklab
2024-02-20 23:58 dpdklab
2024-02-20 23:40 dpdklab
2024-02-20 23:16 dpdklab
2024-02-20 19:28 dpdklab
2024-02-20 18:54 dpdklab
2024-02-20 18:43 dpdklab
2024-02-20 18:40 dpdklab
2024-02-20 18:31 dpdklab
2024-02-20 18:24 dpdklab
2024-02-20 18:17 dpdklab
2024-02-20 18:10 dpdklab
2024-02-20 18:06 dpdklab
2024-02-20 17:57 dpdklab
2024-02-20 17:55 dpdklab
2024-02-20 17:54 dpdklab
2024-02-20 17:53 dpdklab
2024-02-20 17:39 dpdklab
2024-02-20 17:27 dpdklab
2024-02-20 17:07 dpdklab
2024-02-20 17:05 dpdklab
2024-02-20 17:03 dpdklab
2024-02-20 17:03 dpdklab
2024-02-20 17:02 dpdklab
2024-02-20 17:00 dpdklab
2024-02-20 16:57 dpdklab
2024-02-20 16:57 dpdklab
2024-02-20 16:56 dpdklab
2024-02-20 16:55 dpdklab
2024-02-20 16:54 dpdklab
2024-02-20 16:53 dpdklab
2024-02-20 16:53 dpdklab
2024-02-20 16:53 dpdklab
2024-02-20 16:51 dpdklab
2024-02-20 16:48 dpdklab
2024-02-20 16:47 dpdklab
2024-02-20 16:47 dpdklab
2024-02-20 16:45 dpdklab
2024-02-20 16:44 dpdklab
2024-02-20 16:42 dpdklab
2024-02-20 16:40 dpdklab
2024-02-20 16:39 dpdklab
2024-02-20 16:39 dpdklab
2024-02-20 16:22 dpdklab
2024-02-20 16:22 dpdklab
2024-02-20 16:19 dpdklab
2024-02-20 16:17 dpdklab
2024-02-20 16:17 dpdklab
2024-02-20 16:11 dpdklab
2024-02-20 16:11 dpdklab
2024-02-20 16:11 dpdklab
2024-02-20 16:10 dpdklab
2024-02-20 16:07 dpdklab
2024-02-20 16:06 dpdklab
2024-02-20 16:06 dpdklab
2024-02-20 16:04 dpdklab
2024-02-20 15:54 dpdklab
2024-02-20 15:41 dpdklab
2024-02-20 15:39 dpdklab
2024-02-20 15:39 dpdklab
2024-02-20 15:38 dpdklab
2024-02-20 15:38 dpdklab
2024-02-20 15:38 dpdklab
2024-02-20 15:38 dpdklab
2024-02-20 15:37 dpdklab
2024-02-20 15:36 dpdklab
2024-02-20 15:25 dpdklab
2024-02-20 15:24 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=65d4d5bc.170a0220.5163c.640cSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=ndabilpuram@marvell.com \
--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).