From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| [GIT MASTER] 3b3fef9de22af80d173453ab65a80b01ce38cbfd
Date: Tue, 18 Apr 2023 19:24:04 +0000 (UTC) [thread overview]
Message-ID: <20230418192404.681B260095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
_Testing PASS_
Branch: dpdk
3b3fef9de22af80d173453ab65a80b01ce38cbfd --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.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
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)
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
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/24318/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-18 19:24 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 19:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-19 18:04 dpdklab
2023-04-19 18:03 dpdklab
2023-04-19 15:04 dpdklab
2023-04-19 14:56 dpdklab
2023-04-19 14:49 dpdklab
2023-04-19 14:47 dpdklab
2023-04-19 14:26 dpdklab
2023-04-19 14:23 dpdklab
2023-04-19 14:15 dpdklab
2023-04-19 14:10 dpdklab
2023-04-19 14:09 dpdklab
2023-04-19 14:09 dpdklab
2023-04-19 14:08 dpdklab
2023-04-19 14:07 dpdklab
2023-04-19 14:06 dpdklab
2023-04-19 14:03 dpdklab
2023-04-19 14:00 dpdklab
2023-04-19 13:55 dpdklab
2023-04-19 13:51 dpdklab
2023-04-19 13:46 dpdklab
2023-04-19 13:45 dpdklab
2023-04-19 13:44 dpdklab
2023-04-19 13:43 dpdklab
2023-04-19 13:38 dpdklab
2023-04-19 13:37 dpdklab
2023-04-19 13:37 dpdklab
2023-04-19 13:36 dpdklab
2023-04-19 13:35 dpdklab
2023-04-19 13:30 dpdklab
2023-04-19 13:28 dpdklab
2023-04-19 9:37 dpdklab
2023-04-19 9:37 dpdklab
2023-04-19 6:26 dpdklab
2023-04-19 6:25 dpdklab
2023-04-19 4:17 dpdklab
2023-04-19 3:38 dpdklab
2023-04-18 23:45 dpdklab
2023-04-18 23:24 dpdklab
2023-04-18 19:30 dpdklab
2023-04-18 19:22 dpdklab
2023-04-18 18:59 dpdklab
2023-04-18 18:55 dpdklab
2023-04-18 18:54 dpdklab
2023-04-18 18:48 dpdklab
2023-04-18 18:32 dpdklab
2023-04-18 18:02 dpdklab
2023-04-18 17:17 dpdklab
2023-04-18 17:05 dpdklab
2023-04-18 16:51 dpdklab
2023-04-18 16:36 dpdklab
2023-04-18 16:32 dpdklab
2023-04-18 16:31 dpdklab
2023-04-18 16:29 dpdklab
2023-04-18 16:27 dpdklab
2023-04-18 16:17 dpdklab
2023-04-18 16:16 dpdklab
2023-04-18 16:15 dpdklab
2023-04-18 16:12 dpdklab
2023-04-18 16:12 dpdklab
2023-04-18 16:09 dpdklab
2023-04-18 16:07 dpdklab
2023-04-18 16:07 dpdklab
2023-04-18 16:04 dpdklab
2023-04-18 15:55 dpdklab
2023-04-18 15:50 dpdklab
2023-04-18 15:48 dpdklab
2023-04-18 15:43 dpdklab
2023-04-18 15:18 dpdklab
2023-04-18 15:08 dpdklab
2023-04-18 14:59 dpdklab
2023-04-18 14:16 dpdklab
2023-04-18 14:13 dpdklab
2023-04-18 14:09 dpdklab
2023-04-18 14:06 dpdklab
2023-04-18 14:04 dpdklab
2023-04-18 14:04 dpdklab
2023-04-18 14:00 dpdklab
2023-04-18 13:59 dpdklab
2023-04-18 13:59 dpdklab
2023-04-18 13:56 dpdklab
2023-04-18 13:53 dpdklab
2023-04-18 13:52 dpdklab
2023-04-18 13:46 dpdklab
2023-04-12 20:53 dpdklab
2023-04-12 20:53 dpdklab
2023-04-12 20:42 dpdklab
2023-04-12 20:38 dpdklab
2023-04-12 20:35 dpdklab
2023-04-12 20:35 dpdklab
2023-04-12 20:29 dpdklab
2023-04-12 20:22 dpdklab
2023-04-12 20:20 dpdklab
2023-04-12 20:16 dpdklab
2023-04-12 19:32 dpdklab
2023-04-12 19:12 dpdklab
2023-04-12 14:51 dpdklab
2023-04-12 14:50 dpdklab
2023-04-12 14:40 dpdklab
2023-04-12 14:36 dpdklab
2023-04-12 14:29 dpdklab
2023-04-12 14:19 dpdklab
2023-04-12 14:14 dpdklab
2023-04-12 14:12 dpdklab
2023-04-12 14:11 dpdklab
2023-04-12 14:10 dpdklab
2023-04-12 14:10 dpdklab
2023-04-12 14:09 dpdklab
2023-04-12 14:09 dpdklab
2023-04-12 14:05 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=20230418192404.681B260095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).