From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132752 [PATCH] eal: remove return from functions declare
Date: Tue, 17 Oct 2023 18:47:08 -0700 (PDT) [thread overview]
Message-ID: <652f391c.0d0a0220.bc435.9dbdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132752
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, October 17 2023 13:03:39
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:55bc9233a2065b3003e90710e4d139159f7c3ebf
132752 --> testing pass
Test environment and result as below:
+------------------+--------------------+
| Environment | dpdk_meson_compile |
+==================+====================+
| FreeBSD 13 | PASS |
+------------------+--------------------+
| CentOS Stream 9 | PASS |
+------------------+--------------------+
| CentOS Stream 8 | PASS |
+------------------+--------------------+
| Debian Bullseye | PASS |
+------------------+--------------------+
| openSUSE Leap 15 | PASS |
+------------------+--------------------+
| Debian Buster | PASS |
+------------------+--------------------+
| Ubuntu 20.04 | PASS |
+------------------+--------------------+
| Fedora 38 | PASS |
+------------------+--------------------+
| RHEL8 | PASS |
+------------------+--------------------+
| Ubuntu 22.04 | PASS |
+------------------+--------------------+
| Alpine | PASS |
+------------------+--------------------+
| Fedora 37 | PASS |
+------------------+--------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
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 Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.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)
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27969/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-18 1:47 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 1:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-18 16:48 dpdklab
2023-10-18 16:43 dpdklab
2023-10-18 9:24 dpdklab
2023-10-18 5:13 dpdklab
2023-10-18 5:07 dpdklab
2023-10-18 5:00 dpdklab
2023-10-18 4:53 dpdklab
2023-10-18 4:26 dpdklab
2023-10-18 4:26 dpdklab
2023-10-18 3:27 dpdklab
2023-10-18 3:02 dpdklab
2023-10-18 3:01 dpdklab
2023-10-18 3:01 dpdklab
2023-10-18 3:00 dpdklab
2023-10-18 2:57 dpdklab
2023-10-18 2:56 dpdklab
2023-10-18 2:53 dpdklab
2023-10-18 2:47 dpdklab
2023-10-18 2:46 dpdklab
2023-10-18 2:45 dpdklab
2023-10-18 2:45 dpdklab
2023-10-18 2:45 dpdklab
2023-10-18 2:44 dpdklab
2023-10-18 2:42 dpdklab
2023-10-18 2:42 dpdklab
2023-10-18 2:42 dpdklab
2023-10-18 2:42 dpdklab
2023-10-18 2:38 dpdklab
2023-10-18 2:32 dpdklab
2023-10-18 2:29 dpdklab
2023-10-18 2:00 dpdklab
2023-10-18 2:00 dpdklab
2023-10-18 2:00 dpdklab
2023-10-18 1:55 dpdklab
2023-10-18 1:54 dpdklab
2023-10-18 1:47 dpdklab
2023-10-18 1:46 dpdklab
2023-10-18 1:45 dpdklab
2023-10-18 1:44 dpdklab
2023-10-18 1:43 dpdklab
2023-10-18 1:42 dpdklab
2023-10-18 1:41 dpdklab
2023-10-18 1:37 dpdklab
2023-10-18 1:32 dpdklab
2023-10-18 0:02 dpdklab
2023-10-17 23:49 dpdklab
2023-10-17 23:40 dpdklab
2023-10-17 23:40 dpdklab
2023-10-17 23:16 dpdklab
2023-10-17 23:16 dpdklab
2023-10-17 23:12 dpdklab
2023-10-17 22:52 dpdklab
2023-10-17 22:50 dpdklab
2023-10-17 22:49 dpdklab
2023-10-17 22:43 dpdklab
2023-10-17 22:43 dpdklab
2023-10-17 22:21 dpdklab
2023-10-17 22:19 dpdklab
2023-10-17 21:47 dpdklab
2023-10-17 21:42 dpdklab
2023-10-17 21:42 dpdklab
2023-10-17 21:41 dpdklab
2023-10-17 21:41 dpdklab
2023-10-17 21:41 dpdklab
2023-10-17 21:41 dpdklab
2023-10-17 21:40 dpdklab
2023-10-17 21:40 dpdklab
2023-10-17 21:40 dpdklab
2023-10-17 21:40 dpdklab
2023-10-17 21:40 dpdklab
2023-10-17 21:40 dpdklab
2023-10-17 21:40 dpdklab
2023-10-17 21:39 dpdklab
2023-10-17 21:38 dpdklab
2023-10-17 21:38 dpdklab
2023-10-17 21:38 dpdklab
2023-10-17 21:38 dpdklab
2023-10-17 21:38 dpdklab
2023-10-17 21:37 dpdklab
2023-10-17 21:37 dpdklab
2023-10-17 21:37 dpdklab
2023-10-17 21:37 dpdklab
2023-10-17 21:37 dpdklab
2023-10-17 21:35 dpdklab
2023-10-17 21:35 dpdklab
2023-10-17 21:35 dpdklab
2023-10-17 21:28 dpdklab
2023-10-17 21:26 dpdklab
2023-10-17 21:25 dpdklab
2023-10-17 21:06 dpdklab
2023-10-17 21:04 dpdklab
2023-10-17 21:01 dpdklab
2023-10-17 21:01 dpdklab
2023-10-17 20:56 dpdklab
2023-10-17 20:09 dpdklab
2023-10-17 20:00 dpdklab
2023-10-17 19:53 dpdklab
2023-10-17 19:13 dpdklab
2023-10-17 18:38 dpdklab
2023-10-17 18:25 dpdklab
2023-10-17 18:19 dpdklab
2023-10-17 18:12 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=652f391c.0d0a0220.bc435.9dbdSMTPIN_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).