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] e0fb0051ff8f621a2b001d9243cebe50f3d42cf5
Date: Mon, 6 Mar 2023 23:46:09 +0000 (UTC) [thread overview]
Message-ID: <20230306234609.E88C960095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
_Testing PASS_
Branch: dpdk
e0fb0051ff8f621a2b001d9243cebe50f3d42cf5 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| Ubuntu 20.04 | PASS |
+------------------+----------+
| Arch Linux | PASS |
+------------------+----------+
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-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
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
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)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
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/23677/
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-06 23:46 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 23:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-07 13:31 dpdklab
2023-03-07 13:31 dpdklab
2023-03-07 13:30 dpdklab
2023-03-07 13:29 dpdklab
2023-03-07 13:27 dpdklab
2023-03-07 13:23 dpdklab
2023-03-07 13:22 dpdklab
2023-03-07 13:20 dpdklab
2023-03-07 13:12 dpdklab
2023-03-07 13:07 dpdklab
2023-03-07 13:06 dpdklab
2023-03-07 12:59 dpdklab
2023-03-07 12:55 dpdklab
2023-03-07 12:55 dpdklab
2023-03-07 12:53 dpdklab
2023-03-07 12:50 dpdklab
2023-03-07 12:50 dpdklab
2023-03-07 12:36 dpdklab
2023-03-07 12:27 dpdklab
2023-03-07 12:26 dpdklab
2023-03-07 12:25 dpdklab
2023-03-07 12:23 dpdklab
2023-03-07 12:22 dpdklab
2023-03-07 12:21 dpdklab
2023-03-07 12:18 dpdklab
2023-03-07 12:15 dpdklab
2023-03-07 12:15 dpdklab
2023-03-07 12:09 dpdklab
2023-03-06 23:45 dpdklab
2023-03-06 23:45 dpdklab
2023-03-06 23:30 dpdklab
2023-03-06 22:47 dpdklab
2023-03-06 22:45 dpdklab
2023-03-06 22:45 dpdklab
2023-03-06 22:43 dpdklab
2023-03-06 22:43 dpdklab
2023-03-06 22:41 dpdklab
2023-03-06 22:40 dpdklab
2023-03-06 22:39 dpdklab
2023-03-06 22:37 dpdklab
2023-03-06 22:35 dpdklab
2023-03-06 22:34 dpdklab
2023-03-06 22:09 dpdklab
2023-03-06 22:07 dpdklab
2023-03-06 22:02 dpdklab
2023-03-06 19:29 dpdklab
2023-03-06 18:50 dpdklab
2023-03-06 18:37 dpdklab
2023-03-06 18:36 dpdklab
2023-03-06 18:33 dpdklab
2023-03-06 18:28 dpdklab
2023-03-06 18:27 dpdklab
2023-03-06 18:26 dpdklab
2023-03-06 18:23 dpdklab
2023-03-06 18:22 dpdklab
2023-03-06 18:21 dpdklab
2023-03-06 18:18 dpdklab
2023-03-06 18:16 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=20230306234609.E88C960095@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).