From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137199 [PATCH] net/virtio-user: support IOVA as PA mode
Date: Mon, 26 Feb 2024 04:54:36 -0800 (PST) [thread overview]
Message-ID: <65dc8a0c.0d0a0220.4022.2871SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137199
_Testing PASS_
Submitter: Srujana Challa <schalla@marvell.com>
Date: Monday, February 26 2024 11:40:19
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2176806a4052a28bce70fe1767d8a56c6d7e904e
137199 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29261/
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 12:54 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 12:54 dpdklab [this message]
[not found] <20240226114019.2127838-1-schalla@marvell.com>
2024-02-28 0:45 ` dpdklab
2024-02-28 1:00 ` dpdklab
2024-02-28 1:00 ` dpdklab
2024-02-28 1:28 ` dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-26 16:06 dpdklab
2024-02-26 15:38 dpdklab
2024-02-26 15:15 dpdklab
2024-02-26 14:09 dpdklab
2024-02-26 14:02 dpdklab
2024-02-26 13:47 dpdklab
2024-02-26 13:34 dpdklab
2024-02-26 13:27 dpdklab
2024-02-26 13:26 dpdklab
2024-02-26 13:26 dpdklab
2024-02-26 13:23 dpdklab
2024-02-26 13:22 dpdklab
2024-02-26 13:21 dpdklab
2024-02-26 13:19 dpdklab
2024-02-26 13:17 dpdklab
2024-02-26 13:16 dpdklab
2024-02-26 13:16 dpdklab
2024-02-26 13:16 dpdklab
2024-02-26 13:16 dpdklab
2024-02-26 13:15 dpdklab
2024-02-26 13:14 dpdklab
2024-02-26 13:14 dpdklab
2024-02-26 13:14 dpdklab
2024-02-26 13:13 dpdklab
2024-02-26 13:13 dpdklab
2024-02-26 13:13 dpdklab
2024-02-26 13:01 dpdklab
2024-02-26 13:01 dpdklab
2024-02-26 13:00 dpdklab
2024-02-26 13:00 dpdklab
2024-02-26 12:59 dpdklab
2024-02-26 12:59 dpdklab
2024-02-26 12:59 dpdklab
2024-02-26 12:59 dpdklab
2024-02-26 12:59 dpdklab
2024-02-26 12:58 dpdklab
2024-02-26 12:58 dpdklab
2024-02-26 12:57 dpdklab
2024-02-26 12:57 dpdklab
2024-02-26 12:56 dpdklab
2024-02-26 12:56 dpdklab
2024-02-26 12:55 dpdklab
2024-02-26 12:55 dpdklab
2024-02-26 12:54 dpdklab
2024-02-26 12:54 dpdklab
2024-02-26 12:53 dpdklab
2024-02-26 12:53 dpdklab
2024-02-26 12:53 dpdklab
2024-02-26 12:53 dpdklab
2024-02-26 12:52 dpdklab
2024-02-26 12:52 dpdklab
2024-02-26 12:52 dpdklab
2024-02-26 12:51 dpdklab
2024-02-26 12:51 dpdklab
2024-02-26 12:51 dpdklab
2024-02-26 12:50 dpdklab
2024-02-26 12:50 dpdklab
2024-02-26 12:50 dpdklab
2024-02-26 12:49 dpdklab
2024-02-26 12:49 dpdklab
2024-02-26 12:48 dpdklab
2024-02-26 12:45 dpdklab
2024-02-26 12:44 dpdklab
2024-02-26 12:43 dpdklab
2024-02-26 12:34 dpdklab
2024-02-26 12:33 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=65dc8a0c.0d0a0220.4022.2871SMTPIN_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).