From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw140909 [PATCH] maintainers: update email address for PPC
Date: Wed, 12 Jun 2024 16:08:25 -0700 (PDT) [thread overview]
Message-ID: <666a2a69.050a0220.b5303.03b2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240529173420.42401-1-drc@linux.vnet.ibm.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140909
_Testing PASS_
Submitter: David Christensen <drc@linux.vnet.ibm.com>
Date: Wednesday, May 29 2024 17:34:19
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:76cef1af8bdaeaf67a5c4ca5df3f221df994dc46
140909 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian 12 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 39 | PASS |
+---------------------+----------------+
| Ubuntu 24.04 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| RHEL8 | 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 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
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
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
Ubuntu 24.04
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30154/
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-12 23:09 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240529173420.42401-1-drc@linux.vnet.ibm.com>
2024-06-10 15:13 ` qemudev
2024-06-10 15:17 ` qemudev
2024-06-10 15:37 ` |WARNING| " checkpatch
2024-06-10 22:37 ` |SUCCESS| " dpdklab
2024-06-10 22:37 ` dpdklab
2024-06-10 22:38 ` dpdklab
2024-06-10 22:38 ` dpdklab
2024-06-10 22:45 ` dpdklab
2024-06-10 22:46 ` dpdklab
2024-06-12 22:47 ` dpdklab
2024-06-12 22:47 ` dpdklab
2024-06-12 22:48 ` dpdklab
2024-06-12 22:48 ` dpdklab
2024-06-12 22:49 ` dpdklab
2024-06-12 22:50 ` dpdklab
2024-06-12 22:50 ` dpdklab
2024-06-12 22:50 ` dpdklab
2024-06-12 22:51 ` dpdklab
2024-06-12 22:51 ` dpdklab
2024-06-12 22:52 ` dpdklab
2024-06-12 22:52 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:53 ` dpdklab
2024-06-12 22:54 ` dpdklab
2024-06-12 22:54 ` dpdklab
2024-06-12 22:54 ` dpdklab
2024-06-12 22:54 ` dpdklab
2024-06-12 22:55 ` dpdklab
2024-06-12 22:55 ` dpdklab
2024-06-12 22:55 ` dpdklab
2024-06-12 22:55 ` dpdklab
2024-06-12 22:56 ` dpdklab
2024-06-12 22:56 ` dpdklab
2024-06-12 22:56 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:57 ` dpdklab
2024-06-12 22:58 ` dpdklab
2024-06-12 22:58 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:05 ` dpdklab
2024-06-12 23:05 ` dpdklab
2024-06-12 23:05 ` dpdklab
2024-06-12 23:06 ` dpdklab
2024-06-12 23:06 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab [this message]
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:35 ` 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=666a2a69.050a0220.b5303.03b2SMTPIN_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).