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] 9bd5ebca59c865aead7096358fb733e53a72007b
Date: Wed, 22 Feb 2023 07:42:06 +0000 (UTC) [thread overview]
Message-ID: <20230222074206.BF51C600AB@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1880 bytes --]
_Testing PASS_
Branch: dpdk
9bd5ebca59c865aead7096358fb733e53a72007b --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Arch Linux | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Ubuntu 20.04 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
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)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/23418/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-22 7:42 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 7:42 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-21 17:17 dpdklab
2023-02-21 17:10 dpdklab
2023-02-21 17:06 dpdklab
2023-02-21 16:58 dpdklab
2023-02-21 16:58 dpdklab
2023-02-21 16:56 dpdklab
2023-02-21 16:54 dpdklab
2023-02-21 16:52 dpdklab
2023-02-21 16:51 dpdklab
2023-02-21 16:50 dpdklab
2023-02-21 16:50 dpdklab
2023-02-21 16:41 dpdklab
2023-02-21 6:10 dpdklab
2023-02-21 4:15 dpdklab
2023-02-21 4:15 dpdklab
2023-02-21 4:08 dpdklab
2023-02-21 4:07 dpdklab
2023-02-21 4:03 dpdklab
2023-02-21 4:02 dpdklab
2023-02-21 3:57 dpdklab
2023-02-21 3:43 dpdklab
2023-02-21 3:37 dpdklab
2023-02-21 3:32 dpdklab
2023-02-21 3:30 dpdklab
2023-02-21 3:24 dpdklab
2023-02-21 3:21 dpdklab
2023-02-21 0:07 dpdklab
2023-02-20 23:33 dpdklab
2023-02-20 23:26 dpdklab
2023-02-20 23:14 dpdklab
2023-02-20 23:14 dpdklab
2023-02-20 23:13 dpdklab
2023-02-20 23:11 dpdklab
2023-02-20 23:04 dpdklab
2023-02-20 23:02 dpdklab
2023-02-20 23:00 dpdklab
2023-02-20 22:56 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=20230222074206.BF51C600AB@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).