From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139022 [PATCH] build: exclude rather than include libs i
Date: Tue, 02 Apr 2024 16:51:19 -0700 (PDT) [thread overview]
Message-ID: <660c99f7.050a0220.4ed79.c0b4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1712076948-25853-2-git-send-email-roretzla@linux.microsoft.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139022
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, April 02 2024 16:55:48
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139022 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian 12 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 39 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Ubuntu 22.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 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
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
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
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
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
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/29692/
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-04-02 23:51 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1712076948-25853-2-git-send-email-roretzla@linux.microsoft.com>
2024-04-02 16:35 ` |SUCCESS| pw139022 [PATCH] build: exclude rather than include libs in MSVC build qemudev
2024-04-02 16:39 ` qemudev
2024-04-02 16:56 ` checkpatch
2024-04-02 17:45 ` 0-day Robot
2024-04-02 21:59 ` |SUCCESS| pw139022 [PATCH] build: exclude rather than include libs i dpdklab
2024-04-02 22:03 ` dpdklab
2024-04-02 22:20 ` dpdklab
2024-04-02 22:21 ` dpdklab
2024-04-02 22:21 ` dpdklab
2024-04-02 22:22 ` dpdklab
2024-04-02 22:23 ` dpdklab
2024-04-02 22:23 ` dpdklab
2024-04-02 22:24 ` dpdklab
2024-04-02 22:25 ` dpdklab
2024-04-02 22:25 ` dpdklab
2024-04-02 22:26 ` dpdklab
2024-04-02 22:26 ` dpdklab
2024-04-02 22:27 ` dpdklab
2024-04-02 22:29 ` dpdklab
2024-04-02 22:31 ` dpdklab
2024-04-02 22:34 ` dpdklab
2024-04-02 22:37 ` dpdklab
2024-04-02 22:40 ` dpdklab
2024-04-02 22:41 ` dpdklab
2024-04-02 22:42 ` dpdklab
2024-04-02 22:43 ` dpdklab
2024-04-02 22:49 ` dpdklab
2024-04-02 22:50 ` dpdklab
2024-04-02 22:50 ` dpdklab
2024-04-02 22:52 ` dpdklab
2024-04-02 22:54 ` dpdklab
2024-04-02 22:55 ` dpdklab
2024-04-02 22:58 ` dpdklab
2024-04-02 23:01 ` dpdklab
2024-04-02 23:02 ` dpdklab
2024-04-02 23:03 ` dpdklab
2024-04-02 23:04 ` dpdklab
2024-04-02 23:05 ` dpdklab
2024-04-02 23:08 ` dpdklab
2024-04-02 23:08 ` dpdklab
2024-04-02 23:16 ` dpdklab
2024-04-02 23:16 ` dpdklab
2024-04-02 23:19 ` dpdklab
2024-04-02 23:23 ` dpdklab
2024-04-02 23:24 ` dpdklab
2024-04-02 23:26 ` dpdklab
2024-04-02 23:27 ` dpdklab
2024-04-02 23:28 ` dpdklab
2024-04-02 23:28 ` dpdklab
2024-04-02 23:29 ` dpdklab
2024-04-02 23:29 ` dpdklab
2024-04-02 23:31 ` dpdklab
2024-04-02 23:31 ` dpdklab
2024-04-02 23:34 ` dpdklab
2024-04-02 23:35 ` dpdklab
2024-04-02 23:36 ` dpdklab
2024-04-02 23:37 ` dpdklab
2024-04-02 23:37 ` dpdklab
2024-04-02 23:38 ` dpdklab
2024-04-02 23:40 ` dpdklab
2024-04-02 23:41 ` dpdklab
2024-04-02 23:41 ` dpdklab
2024-04-02 23:42 ` dpdklab
2024-04-02 23:43 ` dpdklab
2024-04-02 23:44 ` dpdklab
2024-04-02 23:45 ` dpdklab
2024-04-02 23:45 ` dpdklab
2024-04-02 23:46 ` dpdklab
2024-04-02 23:46 ` dpdklab
2024-04-02 23:47 ` dpdklab
2024-04-02 23:48 ` dpdklab
2024-04-02 23:48 ` dpdklab
2024-04-02 23:48 ` dpdklab
2024-04-02 23:49 ` dpdklab
2024-04-02 23:49 ` dpdklab
2024-04-02 23:50 ` dpdklab
2024-04-02 23:51 ` dpdklab [this message]
2024-04-02 23:51 ` dpdklab
2024-04-02 23:51 ` dpdklab
2024-04-02 23:52 ` dpdklab
2024-04-02 23:53 ` dpdklab
2024-04-02 23:54 ` dpdklab
2024-04-02 23:56 ` dpdklab
2024-04-02 23:57 ` dpdklab
2024-04-03 0:17 ` dpdklab
2024-04-03 1:08 ` dpdklab
2024-04-03 1:09 ` dpdklab
2024-04-03 21:06 ` dpdklab
2024-04-03 21:10 ` dpdklab
2024-04-03 21:15 ` dpdklab
2024-04-03 21:19 ` dpdklab
2024-04-03 21:38 ` dpdklab
2024-04-05 20:48 ` dpdklab
2024-04-05 21:17 ` dpdklab
2024-04-05 21:18 ` dpdklab
2024-04-05 21:18 ` dpdklab
2024-04-05 21:18 ` dpdklab
2024-04-05 21:19 ` dpdklab
2024-04-05 21:21 ` dpdklab
2024-04-05 21:21 ` dpdklab
2024-04-05 21:28 ` dpdklab
2024-04-05 21:29 ` dpdklab
2024-04-05 21:29 ` dpdklab
2024-04-05 21:34 ` dpdklab
2024-04-05 22:08 ` dpdklab
2024-04-06 0:38 ` dpdklab
2024-04-06 1:03 ` 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=660c99f7.050a0220.4ed79.c0b4SMTPIN_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).