From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130477-130481 [PATCH] [v5,6/6] devtools: forbid new dire
Date: Thu, 17 Aug 2023 21:33:43 -0700 (PDT) [thread overview]
Message-ID: <64def4a7.050a0220.7d2a4.24afSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130481
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thursday, August 17 2023 21:42:17
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:971d2b57972919527e27ed683032a71864a2eb56
130477-130481 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27373/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-18 4:33 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 4:33 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-18 20:53 dpdklab
2023-08-18 20:36 dpdklab
2023-08-18 20:31 dpdklab
2023-08-18 20:27 dpdklab
2023-08-18 20:16 dpdklab
2023-08-18 17:55 dpdklab
2023-08-18 5:32 dpdklab
2023-08-18 5:05 dpdklab
2023-08-18 4:55 dpdklab
2023-08-18 4:51 dpdklab
2023-08-18 4:47 dpdklab
2023-08-18 4:45 dpdklab
2023-08-18 4:40 dpdklab
2023-08-18 4:39 dpdklab
2023-08-18 4:37 dpdklab
2023-08-18 4:27 dpdklab
2023-08-18 4:27 dpdklab
2023-08-18 4:26 dpdklab
2023-08-18 4:25 dpdklab
2023-08-18 4:24 dpdklab
2023-08-18 4:24 dpdklab
2023-08-18 4:24 dpdklab
2023-08-18 4:16 dpdklab
2023-08-18 4:11 dpdklab
2023-08-18 4:10 dpdklab
2023-08-18 4:08 dpdklab
2023-08-18 4:07 dpdklab
2023-08-18 4:06 dpdklab
2023-08-18 4:05 dpdklab
2023-08-18 4:04 dpdklab
2023-08-18 4:04 dpdklab
2023-08-18 4:04 dpdklab
2023-08-18 4:03 dpdklab
2023-08-18 4:02 dpdklab
2023-08-18 3:58 dpdklab
2023-08-18 3:56 dpdklab
2023-08-18 3:55 dpdklab
2023-08-18 3:53 dpdklab
2023-08-18 3:53 dpdklab
2023-08-18 3:48 dpdklab
2023-08-18 3:46 dpdklab
2023-08-18 3:43 dpdklab
2023-08-18 3:43 dpdklab
2023-08-18 3:43 dpdklab
2023-08-18 3:43 dpdklab
2023-08-18 3:41 dpdklab
2023-08-18 3:40 dpdklab
2023-08-18 3:39 dpdklab
2023-08-18 3:38 dpdklab
2023-08-18 3:37 dpdklab
2023-08-18 3:37 dpdklab
2023-08-18 3:35 dpdklab
2023-08-18 3:33 dpdklab
2023-08-18 3:29 dpdklab
2023-08-18 3:28 dpdklab
2023-08-18 3:26 dpdklab
2023-08-18 3:26 dpdklab
2023-08-18 3:26 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=64def4a7.050a0220.7d2a4.24afSMTPIN_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).