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] baf13c3135d0c5998fff7edc23fb89412dc89246
Date: Tue, 14 Mar 2023 14:00:40 +0000 (UTC) [thread overview]
Message-ID: <20230314140040.C88536011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
_Testing PASS_
Branch: dpdk
baf13c3135d0c5998fff7edc23fb89412dc89246 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Debian Buster | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Arch Linux | PASS |
+------------------+----------+
| Ubuntu 20.04 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: clang 14.0.5-1.fc36
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/23798/
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-14 14:00 UTC|newest]
Thread overview: 151+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 14:00 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-15 15:50 dpdklab
2023-03-15 15:50 dpdklab
2023-03-15 15:36 dpdklab
2023-03-15 15:25 dpdklab
2023-03-15 15:24 dpdklab
2023-03-15 15:21 dpdklab
2023-03-15 15:19 dpdklab
2023-03-15 15:04 dpdklab
2023-03-15 15:02 dpdklab
2023-03-15 14:59 dpdklab
2023-03-15 14:57 dpdklab
2023-03-15 14:54 dpdklab
2023-03-15 14:41 dpdklab
2023-03-15 14:37 dpdklab
2023-03-15 11:53 dpdklab
2023-03-15 7:19 dpdklab
2023-03-15 2:47 dpdklab
2023-03-14 22:56 dpdklab
2023-03-14 21:52 dpdklab
2023-03-14 16:22 dpdklab
2023-03-14 16:22 dpdklab
2023-03-14 16:10 dpdklab
2023-03-14 16:05 dpdklab
2023-03-14 15:59 dpdklab
2023-03-14 15:58 dpdklab
2023-03-14 15:58 dpdklab
2023-03-14 15:43 dpdklab
2023-03-14 15:41 dpdklab
2023-03-14 15:32 dpdklab
2023-03-14 15:31 dpdklab
2023-03-14 15:25 dpdklab
2023-03-14 15:24 dpdklab
2023-03-14 15:09 dpdklab
2023-03-14 15:08 dpdklab
2023-03-14 12:11 dpdklab
2023-03-14 12:05 dpdklab
2023-03-14 11:53 dpdklab
2023-03-14 11:47 dpdklab
2023-03-14 11:45 dpdklab
2023-03-14 11:43 dpdklab
2023-03-14 11:42 dpdklab
2023-03-14 11:41 dpdklab
2023-03-14 11:40 dpdklab
2023-03-14 11:39 dpdklab
2023-03-14 11:28 dpdklab
2023-03-14 11:27 dpdklab
2023-03-14 11:27 dpdklab
2023-03-14 10:22 dpdklab
2023-03-14 10:20 dpdklab
2023-03-14 9:41 dpdklab
2023-03-14 9:38 dpdklab
2023-03-14 9:37 dpdklab
2023-03-14 9:35 dpdklab
2023-03-14 9:33 dpdklab
2023-03-14 9:30 dpdklab
2023-03-14 9:29 dpdklab
2023-03-14 9:29 dpdklab
2023-03-14 9:28 dpdklab
2023-03-14 9:22 dpdklab
2023-03-14 9:02 dpdklab
2023-03-14 9:01 dpdklab
2023-03-14 8:44 dpdklab
2023-03-14 5:30 dpdklab
2023-03-14 5:30 dpdklab
2023-03-14 4:50 dpdklab
2023-03-14 4:48 dpdklab
2023-03-14 4:46 dpdklab
2023-03-14 4:43 dpdklab
2023-03-14 4:40 dpdklab
2023-03-14 4:39 dpdklab
2023-03-14 4:36 dpdklab
2023-03-14 4:34 dpdklab
2023-03-14 4:33 dpdklab
2023-03-14 4:31 dpdklab
2023-03-14 4:29 dpdklab
2023-03-14 4:26 dpdklab
2023-03-14 4:02 dpdklab
2023-03-14 3:08 dpdklab
2023-03-14 1:40 dpdklab
2023-03-13 23:03 dpdklab
2023-03-13 22:07 dpdklab
2023-03-13 21:42 dpdklab
2023-03-13 21:37 dpdklab
2023-03-13 21:36 dpdklab
2023-03-13 21:36 dpdklab
2023-03-13 21:32 dpdklab
2023-03-13 21:32 dpdklab
2023-03-13 21:29 dpdklab
2023-03-13 21:28 dpdklab
2023-03-13 21:22 dpdklab
2023-03-13 21:22 dpdklab
2023-03-13 21:16 dpdklab
2023-03-13 20:53 dpdklab
2023-03-13 19:17 dpdklab
2023-03-13 18:38 dpdklab
2023-03-13 18:28 dpdklab
2023-03-13 18:28 dpdklab
2023-03-13 18:22 dpdklab
2023-03-13 18:18 dpdklab
2023-03-13 18:17 dpdklab
2023-03-13 18:14 dpdklab
2023-03-13 18:12 dpdklab
2023-03-13 18:12 dpdklab
2023-03-13 18:10 dpdklab
2023-03-13 18:08 dpdklab
2023-03-13 18:08 dpdklab
2023-03-13 18:07 dpdklab
2023-03-13 18:01 dpdklab
2023-03-13 17:52 dpdklab
2023-03-13 17:36 dpdklab
2023-03-13 17:09 dpdklab
2023-03-13 17:03 dpdklab
2023-03-13 17:01 dpdklab
2023-03-13 16:59 dpdklab
2023-03-13 16:57 dpdklab
2023-03-13 16:56 dpdklab
2023-03-13 16:51 dpdklab
2023-03-13 16:50 dpdklab
2023-03-13 16:47 dpdklab
2023-03-13 16:41 dpdklab
2023-03-13 16:36 dpdklab
2023-03-13 16:25 dpdklab
2023-03-13 16:10 dpdklab
2023-03-13 16:06 dpdklab
2023-03-13 16:01 dpdklab
2023-03-13 15:58 dpdklab
2023-03-13 15:57 dpdklab
2023-03-13 15:55 dpdklab
2023-03-13 15:55 dpdklab
2023-03-13 15:53 dpdklab
2023-03-13 15:51 dpdklab
2023-03-13 15:50 dpdklab
2023-03-13 15:45 dpdklab
2023-03-13 15:39 dpdklab
2023-03-13 5:31 dpdklab
2023-03-13 4:03 dpdklab
2023-03-12 22:58 dpdklab
2023-03-12 22:23 dpdklab
2023-03-12 22:19 dpdklab
2023-03-12 22:15 dpdklab
2023-03-12 22:12 dpdklab
2023-03-12 22:10 dpdklab
2023-03-12 22:10 dpdklab
2023-03-12 22:06 dpdklab
2023-03-12 22:04 dpdklab
2023-03-12 22:02 dpdklab
2023-03-12 22:01 dpdklab
2023-03-12 22:00 dpdklab
2023-03-12 21:56 dpdklab
2023-03-12 21:55 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=20230314140040.C88536011D@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).