From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137197 [PATCH] net/virtio-user: support IOVA as PA mode
Date: Mon, 26 Feb 2024 03:42:47 -0800 (PST) [thread overview]
Message-ID: <65dc7937.020a0220.3d919.4decSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137197
_Testing PASS_
Submitter: Srujana Challa <schalla@marvell.com>
Date: Monday, February 26 2024 10:04:39
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2176806a4052a28bce70fe1767d8a56c6d7e904e
137197 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29259/
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-26 11:42 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 11:42 dpdklab [this message]
[not found] <20240226100439.2127008-1-schalla@marvell.com>
2024-02-27 23:51 ` dpdklab
2024-02-27 23:59 ` dpdklab
2024-02-28 0:06 ` dpdklab
2024-02-28 0:11 ` dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-26 13:57 dpdklab
2024-02-26 13:20 dpdklab
2024-02-26 13:06 dpdklab
2024-02-26 12:51 dpdklab
2024-02-26 12:45 dpdklab
2024-02-26 12:44 dpdklab
2024-02-26 12:35 dpdklab
2024-02-26 12:20 dpdklab
2024-02-26 12:19 dpdklab
2024-02-26 12:19 dpdklab
2024-02-26 12:19 dpdklab
2024-02-26 12:16 dpdklab
2024-02-26 12:16 dpdklab
2024-02-26 12:15 dpdklab
2024-02-26 11:55 dpdklab
2024-02-26 11:55 dpdklab
2024-02-26 11:55 dpdklab
2024-02-26 11:54 dpdklab
2024-02-26 11:53 dpdklab
2024-02-26 11:49 dpdklab
2024-02-26 11:49 dpdklab
2024-02-26 11:47 dpdklab
2024-02-26 11:46 dpdklab
2024-02-26 11:44 dpdklab
2024-02-26 11:43 dpdklab
2024-02-26 11:43 dpdklab
2024-02-26 11:43 dpdklab
2024-02-26 11:41 dpdklab
2024-02-26 11:40 dpdklab
2024-02-26 11:38 dpdklab
2024-02-26 11:37 dpdklab
2024-02-26 11:36 dpdklab
2024-02-26 11:36 dpdklab
2024-02-26 11:35 dpdklab
2024-02-26 11:34 dpdklab
2024-02-26 11:32 dpdklab
2024-02-26 11:31 dpdklab
2024-02-26 11:29 dpdklab
2024-02-26 11:29 dpdklab
2024-02-26 11:27 dpdklab
2024-02-26 11:25 dpdklab
2024-02-26 11:22 dpdklab
2024-02-26 11:21 dpdklab
2024-02-26 11:21 dpdklab
2024-02-26 11:19 dpdklab
2024-02-26 11:17 dpdklab
2024-02-26 11:17 dpdklab
2024-02-26 11:16 dpdklab
2024-02-26 11:16 dpdklab
2024-02-26 11:16 dpdklab
2024-02-26 11:14 dpdklab
2024-02-26 11:14 dpdklab
2024-02-26 11:14 dpdklab
2024-02-26 11:13 dpdklab
2024-02-26 11:08 dpdklab
2024-02-26 11:08 dpdklab
2024-02-26 11:07 dpdklab
2024-02-26 11:07 dpdklab
2024-02-26 11:07 dpdklab
2024-02-26 11:06 dpdklab
2024-02-26 11:06 dpdklab
2024-02-26 11:06 dpdklab
2024-02-26 11:05 dpdklab
2024-02-26 11:04 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=65dc7937.020a0220.3d919.4decSMTPIN_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).