From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw140289 [PATCH] [v4] net/af_xdp: fix umem map size for ze
Date: Thu, 23 May 2024 03:12:08 -0700 (PDT) [thread overview]
Message-ID: <664f1678.4a0a0220.c0525.835eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240523080751.2347970-1-frank.du@intel.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140289
_Testing PASS_
Submitter: Frank Du <frank.du@intel.com>
Date: Thursday, May 23 2024 08:07:51
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a012926d36f3feb9d17a51c8f1559f466570ec0a
140289 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian 12 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Fedora 39 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Fedora 39
Kernel: Depends on container host
Compiler: clang 17.0.6
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29997/
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-05-23 10:12 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240523080751.2347970-1-frank.du@intel.com>
2024-05-23 8:01 ` |SUCCESS| pw140289 [PATCH v4] net/af_xdp: fix umem map size for zero copy qemudev
2024-05-23 8:06 ` qemudev
2024-05-23 8:26 ` checkpatch
2024-05-23 9:20 ` |SUCCESS| pw140289 [PATCH] [v4] net/af_xdp: fix umem map size for ze dpdklab
2024-05-23 9:21 ` dpdklab
2024-05-23 9:22 ` |FAILURE| " dpdklab
2024-05-23 9:24 ` |SUCCESS| pw140289 [PATCH v4] net/af_xdp: fix umem map size for zero copy 0-day Robot
2024-05-23 9:30 ` |SUCCESS| pw140289 [PATCH] [v4] net/af_xdp: fix umem map size for ze dpdklab
2024-05-23 9:30 ` dpdklab
2024-05-23 9:31 ` dpdklab
2024-05-23 9:32 ` |FAILURE| " dpdklab
2024-05-23 9:32 ` dpdklab
2024-05-23 9:32 ` |SUCCESS| " dpdklab
2024-05-23 9:33 ` dpdklab
2024-05-23 9:33 ` dpdklab
2024-05-23 9:33 ` dpdklab
2024-05-23 9:34 ` |FAILURE| " dpdklab
2024-05-23 9:35 ` |SUCCESS| " dpdklab
2024-05-23 9:35 ` |FAILURE| " dpdklab
2024-05-23 9:36 ` |SUCCESS| " dpdklab
2024-05-23 9:36 ` |FAILURE| " dpdklab
2024-05-23 9:36 ` |SUCCESS| " dpdklab
2024-05-23 9:37 ` |FAILURE| " dpdklab
2024-05-23 9:37 ` |SUCCESS| " dpdklab
2024-05-23 9:37 ` dpdklab
2024-05-23 9:38 ` dpdklab
2024-05-23 9:38 ` dpdklab
2024-05-23 9:38 ` dpdklab
2024-05-23 9:39 ` dpdklab
2024-05-23 9:39 ` dpdklab
2024-05-23 9:39 ` |FAILURE| " dpdklab
2024-05-23 9:40 ` |SUCCESS| " dpdklab
2024-05-23 9:40 ` |FAILURE| " dpdklab
2024-05-23 9:40 ` |SUCCESS| " dpdklab
2024-05-23 9:40 ` dpdklab
2024-05-23 9:41 ` dpdklab
2024-05-23 9:41 ` dpdklab
2024-05-23 9:41 ` dpdklab
2024-05-23 9:42 ` dpdklab
2024-05-23 9:42 ` dpdklab
2024-05-23 9:42 ` dpdklab
2024-05-23 9:46 ` dpdklab
2024-05-23 9:47 ` |FAILURE| " dpdklab
2024-05-23 9:47 ` |SUCCESS| " dpdklab
2024-05-23 9:48 ` |FAILURE| " dpdklab
2024-05-23 9:48 ` |SUCCESS| " dpdklab
2024-05-23 9:48 ` dpdklab
2024-05-23 9:48 ` dpdklab
2024-05-23 9:49 ` dpdklab
2024-05-23 9:56 ` dpdklab
2024-05-23 9:56 ` dpdklab
2024-05-23 9:57 ` dpdklab
2024-05-23 9:57 ` dpdklab
2024-05-23 9:58 ` |FAILURE| " dpdklab
2024-05-23 9:58 ` |SUCCESS| " dpdklab
2024-05-23 9:59 ` dpdklab
2024-05-23 9:59 ` |FAILURE| " dpdklab
2024-05-23 9:59 ` dpdklab
2024-05-23 10:00 ` dpdklab
2024-05-23 10:00 ` dpdklab
2024-05-23 10:01 ` dpdklab
2024-05-23 10:02 ` |SUCCESS| " dpdklab
2024-05-23 10:05 ` |FAILURE| " dpdklab
2024-05-23 10:05 ` |SUCCESS| " dpdklab
2024-05-23 10:06 ` dpdklab
2024-05-23 10:06 ` dpdklab
2024-05-23 10:06 ` dpdklab
2024-05-23 10:07 ` dpdklab
2024-05-23 10:08 ` |FAILURE| " dpdklab
2024-05-23 10:11 ` |SUCCESS| " dpdklab
2024-05-23 10:12 ` dpdklab [this message]
2024-05-23 10:12 ` |FAILURE| " dpdklab
2024-05-23 10:12 ` |SUCCESS| " dpdklab
2024-05-23 10:12 ` dpdklab
2024-05-23 10:13 ` dpdklab
2024-05-23 10:13 ` dpdklab
2024-05-23 10:15 ` dpdklab
2024-05-23 10:15 ` dpdklab
2024-05-23 10:15 ` dpdklab
2024-05-23 10:15 ` dpdklab
2024-05-23 10:25 ` dpdklab
2024-05-23 10:27 ` dpdklab
2024-05-23 10:40 ` dpdklab
2024-05-23 10:41 ` dpdklab
2024-05-23 10:44 ` dpdklab
2024-05-23 10:44 ` dpdklab
2024-05-23 10:45 ` dpdklab
2024-05-23 10:45 ` dpdklab
2024-05-23 10:49 ` dpdklab
2024-05-23 10:50 ` dpdklab
2024-05-23 11:06 ` 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=664f1678.4a0a0220.c0525.835eSMTPIN_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).