From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139462-139476 [PATCH] [16/16] build: enable vla warnings
Date: Wed, 17 Apr 2024 18:40:29 -0700 (PDT) [thread overview]
Message-ID: <66207a0d.c80a0220.4c6c4.166bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1713397319-26135-17-git-send-email-roretzla@linux.microsoft.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139476
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, April 17 2024 23:41:59
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139462-139476 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Debian 12 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| Fedora 39 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
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)
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
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.6
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
Fedora 39
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 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29811/
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-18 1:40 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1713397319-26135-17-git-send-email-roretzla@linux.microsoft.com>
2024-04-17 23:21 ` |SUCCESS| pw139462-139476 [PATCH 16/16] build: enable vla warnings on Windows built code qemudev
2024-04-17 23:25 ` qemudev
2024-04-17 23:44 ` |SUCCESS| pw139476 " checkpatch
2024-04-18 0:41 ` |SUCCESS| pw139462-139476 [PATCH] [16/16] build: enable vla warnings dpdklab
2024-04-18 0:41 ` dpdklab
2024-04-18 0:42 ` dpdklab
2024-04-18 0:42 ` dpdklab
2024-04-18 0:44 ` |SUCCESS| pw139476 [PATCH 16/16] build: enable vla warnings on Windows built code 0-day Robot
2024-04-18 0:49 ` |SUCCESS| pw139462-139476 [PATCH] [16/16] build: enable vla warnings dpdklab
2024-04-18 0:50 ` dpdklab
2024-04-18 0:51 ` dpdklab
2024-04-18 0:51 ` dpdklab
2024-04-18 0:52 ` dpdklab
2024-04-18 0:52 ` dpdklab
2024-04-18 0:53 ` dpdklab
2024-04-18 0:53 ` dpdklab
2024-04-18 0:53 ` dpdklab
2024-04-18 0:54 ` dpdklab
2024-04-18 0:54 ` dpdklab
2024-04-18 0:55 ` dpdklab
2024-04-18 0:57 ` dpdklab
2024-04-18 0:57 ` dpdklab
2024-04-18 0:57 ` dpdklab
2024-04-18 0:58 ` dpdklab
2024-04-18 1:02 ` dpdklab
2024-04-18 1:04 ` dpdklab
2024-04-18 1:04 ` dpdklab
2024-04-18 1:04 ` dpdklab
2024-04-18 1:09 ` dpdklab
2024-04-18 1:10 ` dpdklab
2024-04-18 1:11 ` dpdklab
2024-04-18 1:11 ` dpdklab
2024-04-18 1:12 ` dpdklab
2024-04-18 1:12 ` dpdklab
2024-04-18 1:12 ` dpdklab
2024-04-18 1:13 ` dpdklab
2024-04-18 1:13 ` dpdklab
2024-04-18 1:14 ` dpdklab
2024-04-18 1:14 ` dpdklab
2024-04-18 1:14 ` dpdklab
2024-04-18 1:17 ` dpdklab
2024-04-18 1:17 ` dpdklab
2024-04-18 1:26 ` dpdklab
2024-04-18 1:28 ` dpdklab
2024-04-18 1:30 ` dpdklab
2024-04-18 1:30 ` dpdklab
2024-04-18 1:31 ` dpdklab
2024-04-18 1:31 ` dpdklab
2024-04-18 1:31 ` dpdklab
2024-04-18 1:32 ` dpdklab
2024-04-18 1:32 ` dpdklab
2024-04-18 1:33 ` dpdklab
2024-04-18 1:33 ` dpdklab
2024-04-18 1:36 ` dpdklab
2024-04-18 1:37 ` dpdklab
2024-04-18 1:37 ` dpdklab
2024-04-18 1:37 ` dpdklab
2024-04-18 1:37 ` dpdklab
2024-04-18 1:38 ` dpdklab
2024-04-18 1:38 ` dpdklab
2024-04-18 1:38 ` dpdklab
2024-04-18 1:38 ` dpdklab
2024-04-18 1:39 ` dpdklab
2024-04-18 1:40 ` dpdklab
2024-04-18 1:40 ` dpdklab [this message]
2024-04-18 1:40 ` dpdklab
2024-04-18 1:40 ` dpdklab
2024-04-18 1:41 ` dpdklab
2024-04-18 1:41 ` dpdklab
2024-04-18 1:41 ` dpdklab
2024-04-18 1:42 ` dpdklab
2024-04-18 1:52 ` dpdklab
2024-04-18 1:54 ` dpdklab
2024-04-18 1:55 ` dpdklab
2024-04-18 1:56 ` dpdklab
2024-04-18 1:57 ` dpdklab
2024-04-18 1:57 ` dpdklab
2024-04-18 1:58 ` dpdklab
2024-04-18 2:00 ` dpdklab
2024-04-18 2:25 ` dpdklab
2024-04-18 2:26 ` dpdklab
2024-04-18 2:32 ` dpdklab
2024-04-18 2:34 ` dpdklab
2024-04-18 2:37 ` dpdklab
2024-04-18 2:42 ` dpdklab
2024-04-18 2:46 ` dpdklab
2024-04-18 2:50 ` dpdklab
2024-04-18 2:53 ` dpdklab
2024-04-18 2:54 ` dpdklab
2024-04-18 2:56 ` dpdklab
2024-04-18 3:35 ` dpdklab
2024-04-18 4:11 ` dpdklab
2024-04-18 4: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=66207a0d.c80a0220.4c6c4.166bSMTPIN_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).