From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| [GIT MASTER] c682c8991963be243dcc3b7cdc9d6984a1961f4e
Date: Wed, 29 Mar 2023 02:20:18 +0000 (UTC) [thread overview]
Message-ID: <20230329022018.B6BC560124@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
_Testing PASS_
Branch: dpdk
c682c8991963be243dcc3b7cdc9d6984a1961f4e --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| CentOS Stream 8 | PASS |
+------------------+----------------+
| CentOS Stream 9 | PASS |
+------------------+----------------+
| Arch Linux | PASS |
+------------------+----------------+
| Debian Buster | PASS |
+------------------+----------------+
| Debian Bullseye | PASS |
+------------------+----------------+
| Ubuntu 22.04 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
| Ubuntu 20.04 | PASS |
+------------------+----------------+
| RHEL8 | PASS |
+------------------+----------------+
| RHEL 7 | PASS |
+------------------+----------------+
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
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
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 11.3.1-2
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
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)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/24082/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-29 2:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 2:20 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-29 19:11 dpdklab
2023-03-29 18:48 dpdklab
2023-03-29 18:21 dpdklab
2023-03-29 18:20 dpdklab
2023-03-29 17:11 dpdklab
2023-03-29 16:45 dpdklab
2023-03-29 16:36 dpdklab
2023-03-29 16:11 dpdklab
2023-03-29 16:06 dpdklab
2023-03-29 16:05 dpdklab
2023-03-29 16:04 dpdklab
2023-03-29 16:01 dpdklab
2023-03-29 16:00 dpdklab
2023-03-29 15:57 dpdklab
2023-03-29 15:57 dpdklab
2023-03-29 15:53 dpdklab
2023-03-29 15:50 dpdklab
2023-03-29 15:50 dpdklab
2023-03-29 15:49 dpdklab
2023-03-29 15:45 dpdklab
2023-03-29 15:45 dpdklab
2023-03-29 15:42 dpdklab
2023-03-29 8:39 dpdklab
2023-03-29 5:31 dpdklab
2023-03-29 4:33 dpdklab
2023-03-29 4:32 dpdklab
2023-03-29 2:47 dpdklab
2023-03-28 22:23 dpdklab
2023-03-28 22:19 dpdklab
2023-03-28 22:15 dpdklab
2023-03-28 22:14 dpdklab
2023-03-28 22:11 dpdklab
2023-03-28 22:10 dpdklab
2023-03-28 22:09 dpdklab
2023-03-28 22:05 dpdklab
2023-03-28 22:05 dpdklab
2023-03-28 22:03 dpdklab
2023-03-28 22:02 dpdklab
2023-03-28 22:00 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=20230329022018.B6BC560124@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).