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] 70cc4e1fed665712e68f2f45d98dda4abc6accda
Date: Sun, 23 Apr 2023 15:32:00 -0700 (PDT) [thread overview]
Message-ID: <6445b1e0.050a0220.6212b.266fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk
70cc4e1fed665712e68f2f45d98dda4abc6accda --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| RHEL8 | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
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 22.04
Kernel: Container Host Kernel
Compiler: clang 14.0.5-1.fc36
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
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/24381/
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-23 22:32 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 22:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-24 18:59 dpdklab
2023-04-24 16:26 dpdklab
2023-04-24 16:02 dpdklab
2023-04-24 15:59 dpdklab
2023-04-24 15:58 dpdklab
2023-04-24 15:54 dpdklab
2023-04-24 15:52 dpdklab
2023-04-24 15:49 dpdklab
2023-04-24 15:31 dpdklab
2023-04-24 15:25 dpdklab
2023-04-24 15:24 dpdklab
2023-04-24 15:22 dpdklab
2023-04-24 15:21 dpdklab
2023-04-24 15:14 dpdklab
2023-04-24 14:59 dpdklab
2023-04-24 14:53 dpdklab
2023-04-24 14:39 dpdklab
2023-04-24 14:33 dpdklab
2023-04-24 14:28 dpdklab
2023-04-24 14:25 dpdklab
2023-04-24 14:20 dpdklab
2023-04-24 14:15 dpdklab
2023-04-24 14:09 dpdklab
2023-04-24 14:06 dpdklab
2023-04-24 14:04 dpdklab
2023-04-24 14:04 dpdklab
2023-04-24 14:03 dpdklab
2023-04-24 13:59 dpdklab
2023-04-24 13:57 dpdklab
2023-04-23 23:26 dpdklab
2023-04-23 23:26 dpdklab
2023-04-23 23:24 dpdklab
2023-04-23 23:24 dpdklab
2023-04-23 23:10 dpdklab
2023-04-23 23:07 dpdklab
2023-04-23 22:59 dpdklab
2023-04-23 22:49 dpdklab
2023-04-23 22:49 dpdklab
2023-04-23 22:45 dpdklab
2023-04-23 22:37 dpdklab
2023-04-23 22:34 dpdklab
2023-04-23 22:32 dpdklab
2023-04-23 22:29 dpdklab
2023-04-23 22:27 dpdklab
2023-04-23 22:22 dpdklab
2023-04-23 22:20 dpdklab
2023-04-23 22:19 dpdklab
2023-04-23 22:14 dpdklab
2023-04-23 22:11 dpdklab
2023-04-23 22:10 dpdklab
2023-04-23 22:09 dpdklab
2023-04-23 22:09 dpdklab
2023-04-23 22:05 dpdklab
2023-04-23 22:05 dpdklab
2023-04-23 22:03 dpdklab
2023-04-23 22:03 dpdklab
2023-04-23 22:02 dpdklab
2023-04-23 21:58 dpdklab
2023-04-23 21: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=6445b1e0.050a0220.6212b.266fSMTPIN_ADDED_MISSING@mx.google.com \
--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).