From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw140759-140763 [PATCH] [v3,5/5] dts: add `show port stats
Date: Wed, 05 Jun 2024 16:00:23 -0700 (PDT) [thread overview]
Message-ID: <6660ee07.630a0220.eb6ea.108dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240605144504.361438-6-luca.vizzarro@arm.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140763
_Testing PASS_
Submitter: Luca Vizzarro <luca.vizzarro@arm.com>
Date: Wednesday, June 05 2024 14:45:04
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:76cef1af8bdaeaf67a5c4ca5df3f221df994dc46
140759-140763 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian 12 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Fedora 39 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
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 Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30117/
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-06-05 23:00 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240605144504.361438-6-luca.vizzarro@arm.com>
2024-06-05 14:47 ` |SUCCESS| pw140763 [PATCH v3 5/5] dts: add show port stats command to TestPmdShell checkpatch
2024-06-05 15:44 ` |SUCCESS| pw140763 [PATCH v3 5/5] dts: add `show port stats` " 0-day Robot
2024-06-05 20:49 ` |SUCCESS| pw140759-140763 [PATCH] [v3,5/5] dts: add `show port stats dpdklab
2024-06-05 21:14 ` dpdklab
2024-06-05 21:15 ` dpdklab
2024-06-05 21:16 ` dpdklab
2024-06-05 21:17 ` dpdklab
2024-06-05 21:18 ` dpdklab
2024-06-05 21:18 ` dpdklab
2024-06-05 21:19 ` dpdklab
2024-06-05 21:19 ` dpdklab
2024-06-05 21:21 ` dpdklab
2024-06-05 21:22 ` dpdklab
2024-06-05 21:27 ` dpdklab
2024-06-05 21:33 ` dpdklab
2024-06-05 21:33 ` dpdklab
2024-06-05 21:35 ` dpdklab
2024-06-05 21:36 ` dpdklab
2024-06-05 21:36 ` dpdklab
2024-06-05 21:36 ` dpdklab
2024-06-05 21:38 ` dpdklab
2024-06-05 21:39 ` dpdklab
2024-06-05 21:39 ` dpdklab
2024-06-05 21:40 ` dpdklab
2024-06-05 21:41 ` dpdklab
2024-06-05 21:41 ` dpdklab
2024-06-05 21:42 ` dpdklab
2024-06-05 21:42 ` dpdklab
2024-06-05 21:42 ` dpdklab
2024-06-05 21:43 ` dpdklab
2024-06-05 21:43 ` dpdklab
2024-06-05 21:44 ` dpdklab
2024-06-05 21:44 ` dpdklab
2024-06-05 21:45 ` dpdklab
2024-06-05 21:45 ` dpdklab
2024-06-05 21:46 ` dpdklab
2024-06-05 21:48 ` dpdklab
2024-06-05 21:51 ` dpdklab
2024-06-05 21:52 ` dpdklab
2024-06-05 21:52 ` dpdklab
2024-06-05 21:53 ` dpdklab
2024-06-05 21:53 ` dpdklab
2024-06-05 21:53 ` dpdklab
2024-06-05 21:54 ` dpdklab
2024-06-05 21:55 ` dpdklab
2024-06-05 21:55 ` dpdklab
2024-06-05 21:56 ` dpdklab
2024-06-05 21:57 ` dpdklab
2024-06-05 21:57 ` dpdklab
2024-06-05 21:59 ` dpdklab
2024-06-05 21:59 ` dpdklab
2024-06-05 22:02 ` dpdklab
2024-06-05 22:02 ` dpdklab
2024-06-05 22:03 ` dpdklab
2024-06-05 22:04 ` dpdklab
2024-06-05 22:05 ` dpdklab
2024-06-05 22:15 ` dpdklab
2024-06-05 22:16 ` dpdklab
2024-06-05 22:17 ` dpdklab
2024-06-05 22:17 ` dpdklab
2024-06-05 22:18 ` dpdklab
2024-06-05 22:19 ` dpdklab
2024-06-05 22:21 ` dpdklab
2024-06-05 22:24 ` dpdklab
2024-06-05 22:25 ` dpdklab
2024-06-05 22:26 ` dpdklab
2024-06-05 22:27 ` dpdklab
2024-06-05 22:29 ` dpdklab
2024-06-05 22:30 ` dpdklab
2024-06-05 22:31 ` dpdklab
2024-06-05 22:32 ` dpdklab
2024-06-05 22:34 ` dpdklab
2024-06-05 22:35 ` dpdklab
2024-06-05 22:37 ` dpdklab
2024-06-05 22:37 ` dpdklab
2024-06-05 22:40 ` dpdklab
2024-06-05 22:43 ` dpdklab
2024-06-05 22:44 ` dpdklab
2024-06-05 22:50 ` dpdklab
2024-06-05 22:51 ` dpdklab
2024-06-05 22:51 ` dpdklab
2024-06-05 22:53 ` dpdklab
2024-06-05 22:53 ` dpdklab
2024-06-05 22:55 ` dpdklab
2024-06-05 22:57 ` dpdklab
2024-06-05 22:59 ` dpdklab
2024-06-05 23:00 ` dpdklab [this message]
2024-06-05 23:01 ` dpdklab
2024-06-05 23:03 ` dpdklab
2024-06-05 23:04 ` dpdklab
2024-06-05 23:04 ` dpdklab
2024-06-05 23:07 ` dpdklab
2024-06-05 23:09 ` dpdklab
2024-06-05 23:15 ` dpdklab
2024-06-05 23:54 ` dpdklab
2024-06-06 2:31 ` dpdklab
2024-06-06 5:18 ` dpdklab
2024-06-06 5:25 ` dpdklab
2024-06-06 5:50 ` 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=6660ee07.630a0220.eb6ea.108dSMTPIN_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).