From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] abaa473297cf21cb81e5348185a7694ae2f221e7
Date: Fri, 09 Jun 2023 15:06:59 -0700 (PDT) [thread overview]
Message-ID: <6483a283.050a0220.d64e6.8622SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
abaa473297cf21cb81e5348185a7694ae2f221e7 --> testing pass
Test environment and result as below:
+------------------+--------------------+
| Environment | dpdk_meson_compile |
+==================+====================+
| FreeBSD 13 | PASS |
+------------------+--------------------+
| CentOS Stream 9 | PASS |
+------------------+--------------------+
| Debian Buster | PASS |
+------------------+--------------------+
| openSUSE Leap 15 | PASS |
+------------------+--------------------+
| Fedora 37 | PASS |
+------------------+--------------------+
| Debian Bullseye | PASS |
+------------------+--------------------+
| RHEL 7 | PASS |
+------------------+--------------------+
| RHEL8 | PASS |
+------------------+--------------------+
| Ubuntu 20.04 | PASS |
+------------------+--------------------+
| Fedora 38 | PASS |
+------------------+--------------------+
| Alpine | PASS |
+------------------+--------------------+
| CentOS Stream 8 | PASS |
+------------------+--------------------+
| Ubuntu 22.04 | PASS |
+------------------+--------------------+
| Arch Linux | 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
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
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
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
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 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/24847/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-09 22:07 UTC|newest]
Thread overview: 126+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 22:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-09 23:05 dpdklab
2023-06-09 22:31 dpdklab
2023-06-09 22:31 dpdklab
2023-06-09 22:30 dpdklab
2023-06-09 22:30 dpdklab
2023-06-09 22:30 dpdklab
2023-06-09 22:29 dpdklab
2023-06-09 22:20 dpdklab
2023-06-09 22:19 dpdklab
2023-06-09 22:19 dpdklab
2023-06-09 22:19 dpdklab
2023-06-09 22:19 dpdklab
2023-06-09 22:18 dpdklab
2023-06-09 22:14 dpdklab
2023-06-09 22:13 dpdklab
2023-06-09 22:13 dpdklab
2023-06-09 22:12 dpdklab
2023-06-09 22:12 dpdklab
2023-06-09 22:09 dpdklab
2023-06-09 22:07 dpdklab
2023-06-09 22:06 dpdklab
2023-06-09 22:06 dpdklab
2023-06-09 22:06 dpdklab
2023-06-09 22:06 dpdklab
2023-06-09 22:02 dpdklab
2023-06-09 22:02 dpdklab
2023-06-09 22:02 dpdklab
2023-06-09 22:01 dpdklab
2023-06-08 22:02 dpdklab
2023-06-08 22:02 dpdklab
2023-06-08 22:02 dpdklab
2023-06-08 22:01 dpdklab
2023-06-08 22:01 dpdklab
2023-06-08 22:01 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 21:59 dpdklab
2023-06-08 21:59 dpdklab
2023-06-08 21:59 dpdklab
2023-06-08 21:59 dpdklab
2023-06-08 21:59 dpdklab
2023-06-08 21:59 dpdklab
2023-06-08 21:59 dpdklab
2023-06-05 2:03 dpdklab
2023-06-05 1:57 dpdklab
2023-06-05 1:54 dpdklab
2023-06-05 1:37 dpdklab
2023-06-05 1:33 dpdklab
2023-06-05 1:27 dpdklab
2023-06-05 1:23 dpdklab
2023-06-05 1:11 dpdklab
2023-06-05 1:10 dpdklab
2023-06-05 1:05 dpdklab
2023-06-05 1:04 dpdklab
2023-06-05 1:04 dpdklab
2023-06-05 1:03 dpdklab
2023-06-05 1:03 dpdklab
2023-06-04 1:59 dpdklab
2023-06-04 1:54 dpdklab
2023-06-04 1:44 dpdklab
2023-06-04 1:39 dpdklab
2023-06-04 1:35 dpdklab
2023-06-04 1:22 dpdklab
2023-06-04 1:10 dpdklab
2023-06-04 1:10 dpdklab
2023-06-04 1:03 dpdklab
2023-06-04 1:03 dpdklab
2023-06-04 1:02 dpdklab
2023-06-04 0:58 dpdklab
2023-06-04 0:57 dpdklab
2023-06-04 0:56 dpdklab
2023-06-03 2:50 dpdklab
2023-06-03 2:40 dpdklab
2023-06-03 2:35 dpdklab
2023-06-03 2:30 dpdklab
2023-06-03 2:14 dpdklab
2023-06-03 2:10 dpdklab
2023-06-03 1:23 dpdklab
2023-06-03 1:11 dpdklab
2023-06-03 1:10 dpdklab
2023-06-03 1:05 dpdklab
2023-06-03 1:05 dpdklab
2023-06-03 1:05 dpdklab
2023-06-03 1:04 dpdklab
2023-06-03 1:03 dpdklab
2023-06-02 20:54 dpdklab
2023-06-02 20:42 dpdklab
2023-06-02 20:25 dpdklab
2023-06-02 20:18 dpdklab
2023-06-02 20:09 dpdklab
2023-06-02 20:00 dpdklab
2023-06-02 19:48 dpdklab
2023-06-02 19:48 dpdklab
2023-06-02 19:44 dpdklab
2023-06-02 19:41 dpdklab
2023-06-02 19:41 dpdklab
2023-06-02 19:39 dpdklab
2023-06-02 19:35 dpdklab
2023-06-02 19:34 dpdklab
2023-06-02 2:07 dpdklab
2023-06-02 2:06 dpdklab
2023-06-02 1:47 dpdklab
2023-06-02 1:40 dpdklab
2023-06-02 1:23 dpdklab
2023-06-02 1:23 dpdklab
2023-06-02 1:11 dpdklab
2023-06-02 1:10 dpdklab
2023-06-02 1:04 dpdklab
2023-06-02 1:03 dpdklab
2023-06-02 1:02 dpdklab
2023-06-02 0:58 dpdklab
2023-06-02 0:58 dpdklab
2023-06-02 0:57 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=6483a283.050a0220.d64e6.8622SMTPIN_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).