From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138484 [PATCH] net/ixgbe: using dpdk-dumpcap capture pac
Date: Tue, 19 Mar 2024 09:56:30 -0700 (PDT) [thread overview]
Message-ID: <65f9c3be.050a0220.0520.d6fbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1710865092-2796-1-git-send-email-junwang01@cestc.cn>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138484
_Testing PASS_
Submitter: Jun Wang <junwang01@cestc.cn>
Date: Tuesday, March 19 2024 16:18:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2c54ea7a59dfc0a819d3527309c62846fc8853af
138484 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian 11 (arm) | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | PASS |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Alpine | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 14.0.5
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
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)
Alpine
Kernel: 5.4.0-167-generic
Compiler: gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29597/
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-03-19 16:56 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1710865092-2796-1-git-send-email-junwang01@cestc.cn>
2024-03-19 16:00 ` |SUCCESS| pw138484 [PATCH] net/ixgbe: using dpdk-dumpcap capture packet coredump qemudev
2024-03-19 16:05 ` qemudev
2024-03-19 16:18 ` |WARNING| " checkpatch
2024-03-19 16:55 ` |SUCCESS| pw138484 [PATCH] net/ixgbe: using dpdk-dumpcap capture pac dpdklab
2024-03-19 16:55 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:56 ` dpdklab [this message]
2024-03-19 16:56 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:57 ` dpdklab
2024-03-19 16:57 ` dpdklab
2024-03-19 16:57 ` dpdklab
2024-03-19 16:57 ` dpdklab
2024-03-19 16:58 ` dpdklab
2024-03-19 16:58 ` dpdklab
2024-03-19 16:58 ` dpdklab
2024-03-19 16:59 ` dpdklab
2024-03-19 16:59 ` dpdklab
2024-03-19 16:59 ` dpdklab
2024-03-19 17:00 ` dpdklab
2024-03-19 17:00 ` dpdklab
2024-03-19 17:00 ` dpdklab
2024-03-19 17:01 ` dpdklab
2024-03-19 17:02 ` dpdklab
2024-03-19 17:03 ` dpdklab
2024-03-19 17:03 ` dpdklab
2024-03-19 17:03 ` dpdklab
2024-03-19 17:03 ` dpdklab
2024-03-19 17:04 ` dpdklab
2024-03-19 17:04 ` dpdklab
2024-03-19 17:04 ` dpdklab
2024-03-19 17:04 ` dpdklab
2024-03-19 17:05 ` dpdklab
2024-03-19 17:05 ` dpdklab
2024-03-19 17:05 ` dpdklab
2024-03-19 17:05 ` dpdklab
2024-03-19 17:06 ` dpdklab
2024-03-19 17:06 ` dpdklab
2024-03-19 17:07 ` dpdklab
2024-03-19 17:13 ` dpdklab
2024-03-19 17:13 ` dpdklab
2024-03-19 17:14 ` dpdklab
2024-03-19 17:14 ` dpdklab
2024-03-19 17:14 ` dpdklab
2024-03-19 17:14 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:16 ` dpdklab
2024-03-19 17:23 ` |SUCCESS| pw138484 [PATCH] net/ixgbe: using dpdk-dumpcap capture packet coredump 0-day Robot
2024-03-19 17:25 ` |SUCCESS| pw138484 [PATCH] net/ixgbe: using dpdk-dumpcap capture pac dpdklab
2024-03-19 17:26 ` dpdklab
2024-03-19 17:27 ` dpdklab
2024-03-19 17:27 ` dpdklab
2024-03-19 17:28 ` dpdklab
2024-03-19 17:28 ` dpdklab
2024-03-19 17:28 ` dpdklab
2024-03-19 17:28 ` dpdklab
2024-03-19 17:30 ` dpdklab
2024-03-19 17:30 ` dpdklab
2024-03-19 17:30 ` |FAILURE| " dpdklab
2024-03-19 17:31 ` dpdklab
2024-03-19 17:31 ` |SUCCESS| " dpdklab
2024-03-19 17:32 ` |FAILURE| " dpdklab
2024-03-19 17:36 ` dpdklab
2024-03-19 17:41 ` |SUCCESS| " dpdklab
2024-03-19 17:41 ` dpdklab
2024-03-19 17:52 ` dpdklab
2024-03-19 18:05 ` dpdklab
2024-03-19 18:06 ` |FAILURE| " dpdklab
2024-03-19 18:08 ` |SUCCESS| " dpdklab
2024-03-19 18:11 ` dpdklab
2024-03-19 18:48 ` dpdklab
2024-03-21 5:40 ` dpdklab
2024-03-21 6:05 ` 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=65f9c3be.050a0220.0520.d6fbSMTPIN_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).