From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] a526461b0764de52b09b073df84f9e87ec120c93
Date: Tue, 05 Dec 2023 07:02:50 -0800 (PST) [thread overview]
Message-ID: <656f3b9a.250a0220.8fb8c.974eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-eventdev
a526461b0764de52b09b073df84f9e87ec120c93 --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| Debian Buster | PASS |
+------------------+----------------+
| CentOS Stream 8 | PASS |
+------------------+----------------+
| CentOS Stream 9 | PASS |
+------------------+----------------+
| Fedora 37 | PASS |
+------------------+----------------+
| Debian Bullseye | PASS |
+------------------+----------------+
| Fedora 38 | PASS |
+------------------+----------------+
| RHEL8 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
| Ubuntu 22.04 | PASS |
+------------------+----------------+
| Ubuntu 20.04 | PASS |
+------------------+----------------+
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
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
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27219/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-05 15:02 UTC|newest]
Thread overview: 151+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 15:02 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-06 15:02 dpdklab
2023-12-06 4:49 dpdklab
2023-12-06 2:32 dpdklab
2023-12-06 2:27 dpdklab
2023-12-06 2:20 dpdklab
2023-12-06 2:19 dpdklab
2023-12-06 2:18 dpdklab
2023-12-06 2:18 dpdklab
2023-12-06 2:17 dpdklab
2023-12-06 2:16 dpdklab
2023-12-06 2:16 dpdklab
2023-12-06 2:12 dpdklab
2023-12-06 2:11 dpdklab
2023-12-06 2:11 dpdklab
2023-12-06 2:09 dpdklab
2023-12-06 2:09 dpdklab
2023-12-06 2:09 dpdklab
2023-12-06 2:09 dpdklab
2023-12-06 2:08 dpdklab
2023-12-06 2:08 dpdklab
2023-12-06 2:08 dpdklab
2023-12-06 2:08 dpdklab
2023-12-06 2:07 dpdklab
2023-12-06 2:07 dpdklab
2023-12-06 2:06 dpdklab
2023-12-06 2:06 dpdklab
2023-12-06 2:06 dpdklab
2023-12-06 2:06 dpdklab
2023-12-06 2:05 dpdklab
2023-12-06 2:05 dpdklab
2023-12-06 2:05 dpdklab
2023-12-06 2:05 dpdklab
2023-12-06 2:05 dpdklab
2023-12-06 2:04 dpdklab
2023-12-06 2:04 dpdklab
2023-12-06 2:04 dpdklab
2023-12-06 2:04 dpdklab
2023-12-06 2:04 dpdklab
2023-12-06 2:03 dpdklab
2023-12-06 2:03 dpdklab
2023-12-06 2:03 dpdklab
2023-12-06 2:02 dpdklab
2023-12-06 2:02 dpdklab
2023-12-06 2:01 dpdklab
2023-12-06 2:00 dpdklab
2023-12-06 1:58 dpdklab
2023-12-05 17:47 dpdklab
2023-12-05 16:30 dpdklab
2023-12-05 15:46 dpdklab
2023-12-05 15:30 dpdklab
2023-12-05 15:25 dpdklab
2023-12-05 15:25 dpdklab
2023-12-05 15:18 dpdklab
2023-12-05 15:17 dpdklab
2023-12-05 15:14 dpdklab
2023-12-05 15:12 dpdklab
2023-12-05 15:11 dpdklab
2023-12-05 15:11 dpdklab
2023-12-05 15:11 dpdklab
2023-12-05 15:09 dpdklab
2023-12-05 15:09 dpdklab
2023-12-05 15:09 dpdklab
2023-12-05 15:09 dpdklab
2023-12-05 15:09 dpdklab
2023-12-05 15:08 dpdklab
2023-12-05 15:08 dpdklab
2023-12-05 15:08 dpdklab
2023-12-05 15:08 dpdklab
2023-12-05 15:08 dpdklab
2023-12-05 15:08 dpdklab
2023-12-05 15:08 dpdklab
2023-12-05 15:06 dpdklab
2023-12-05 15:06 dpdklab
2023-12-05 15:04 dpdklab
2023-12-05 15:03 dpdklab
2023-12-05 15:02 dpdklab
2023-12-05 15:02 dpdklab
2023-12-05 15:01 dpdklab
2023-12-05 14:55 dpdklab
2023-12-05 14:54 dpdklab
2023-12-05 14:54 dpdklab
2023-12-05 14:53 dpdklab
2023-12-05 14:53 dpdklab
2023-12-05 14:53 dpdklab
2023-12-05 14:50 dpdklab
2023-12-05 14:50 dpdklab
2023-12-05 14:24 dpdklab
2023-12-05 14:24 dpdklab
2023-12-05 14:22 dpdklab
2023-12-05 14:21 dpdklab
2023-12-05 14:16 dpdklab
2023-12-05 14:11 dpdklab
2023-12-05 5:04 dpdklab
2023-12-05 4:01 dpdklab
2023-12-05 3:58 dpdklab
2023-12-05 3:47 dpdklab
2023-12-05 2:36 dpdklab
2023-12-05 2:33 dpdklab
2023-12-05 2:29 dpdklab
2023-12-05 2:29 dpdklab
2023-12-05 2:29 dpdklab
2023-12-05 2:25 dpdklab
2023-12-05 2:25 dpdklab
2023-12-05 2:23 dpdklab
2023-12-05 2:22 dpdklab
2023-12-05 2:22 dpdklab
2023-12-05 2:22 dpdklab
2023-12-05 2:21 dpdklab
2023-12-05 2:21 dpdklab
2023-12-05 2:18 dpdklab
2023-12-05 2:18 dpdklab
2023-12-05 2:18 dpdklab
2023-12-05 2:18 dpdklab
2023-12-05 2:17 dpdklab
2023-12-05 2:17 dpdklab
2023-12-05 2:17 dpdklab
2023-12-05 2:14 dpdklab
2023-12-05 2:13 dpdklab
2023-12-05 2:12 dpdklab
2023-12-05 2:12 dpdklab
2023-12-05 2:11 dpdklab
2023-12-05 2:11 dpdklab
2023-12-05 2:11 dpdklab
2023-12-05 2:10 dpdklab
2023-12-05 2:10 dpdklab
2023-12-05 2:09 dpdklab
2023-12-05 2:09 dpdklab
2023-12-05 2:09 dpdklab
2023-12-05 2:09 dpdklab
2023-12-05 2:08 dpdklab
2023-12-05 2:08 dpdklab
2023-12-05 2:08 dpdklab
2023-12-05 2:08 dpdklab
2023-12-05 2:08 dpdklab
2023-12-05 2:08 dpdklab
2023-12-05 2:08 dpdklab
2023-12-05 2:07 dpdklab
2023-12-05 2:07 dpdklab
2023-12-05 2:07 dpdklab
2023-12-05 2:06 dpdklab
2023-12-05 2:06 dpdklab
2023-12-05 2:06 dpdklab
2023-12-05 2:05 dpdklab
2023-12-05 2:05 dpdklab
2023-12-05 2:04 dpdklab
2023-12-05 2:04 dpdklab
2023-12-05 2:04 dpdklab
2023-12-05 2:04 dpdklab
2023-12-05 2:03 dpdklab
2023-12-05 2:03 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=656f3b9a.250a0220.8fb8c.974eSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
/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).