From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] f8ecc0053ca52cb2310a9e1834ea583167a793cd
Date: Fri, 02 Feb 2024 02:43:34 -0800 (PST) [thread overview]
Message-ID: <65bcc756.050a0220.a700b.4110SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
f8ecc0053ca52cb2310a9e1834ea583167a793cd --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| CentOS Stream 9 | PASS |
+------------------+----------------+
| Debian Buster | PASS |
+------------------+----------------+
| Debian Bullseye | PASS |
+------------------+----------------+
| CentOS Stream 8 | PASS |
+------------------+----------------+
| Fedora 37 | PASS |
+------------------+----------------+
| RHEL8 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
| Fedora 38 | PASS |
+------------------+----------------+
| Ubuntu 20.04 | PASS |
+------------------+----------------+
| Ubuntu 22.04 | PASS |
+------------------+----------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
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
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.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
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27884/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-02 10:43 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 10:43 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-02 15:36 dpdklab
2024-02-02 14:59 dpdklab
2024-02-02 13:20 dpdklab
2024-02-02 11:16 dpdklab
2024-02-02 11:08 dpdklab
2024-02-02 10:48 dpdklab
2024-02-02 10:48 dpdklab
2024-02-02 10:47 dpdklab
2024-02-02 10:47 dpdklab
2024-02-02 10:44 dpdklab
2024-02-02 10:43 dpdklab
2024-02-02 10:42 dpdklab
2024-02-02 10:41 dpdklab
2024-02-02 10:41 dpdklab
2024-02-02 10:39 dpdklab
2024-02-02 10:39 dpdklab
2024-02-02 10:39 dpdklab
2024-02-02 10:38 dpdklab
2024-02-02 10:37 dpdklab
2024-02-02 10:36 dpdklab
2024-02-02 10:35 dpdklab
2024-02-02 10:05 dpdklab
2024-02-02 10:04 dpdklab
2024-02-02 10:02 dpdklab
2024-02-02 9:59 dpdklab
2024-02-02 9:58 dpdklab
2024-02-02 9:56 dpdklab
2024-02-02 9:56 dpdklab
2024-02-02 9:56 dpdklab
2024-02-02 9:55 dpdklab
2024-02-02 9:54 dpdklab
2024-02-02 9:54 dpdklab
2024-02-02 9:53 dpdklab
2024-02-02 9:48 dpdklab
2024-02-02 9:48 dpdklab
2024-02-02 9:44 dpdklab
2024-02-02 9:44 dpdklab
2024-02-02 9:44 dpdklab
2024-02-02 9:43 dpdklab
2024-02-02 9:43 dpdklab
2024-02-02 9:43 dpdklab
2024-02-02 9:43 dpdklab
2024-02-02 9:42 dpdklab
2024-02-02 9:38 dpdklab
2024-02-02 9:33 dpdklab
2024-02-02 9:33 dpdklab
2024-02-02 9:31 dpdklab
2024-02-02 9:06 dpdklab
2024-02-02 9:01 dpdklab
2024-02-02 9:00 dpdklab
2024-02-02 8:59 dpdklab
2024-02-02 8:57 dpdklab
2024-02-02 8:55 dpdklab
2024-02-02 8:53 dpdklab
2024-02-02 8:53 dpdklab
2024-02-02 8:50 dpdklab
2024-02-02 8:49 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=65bcc756.050a0220.a700b.4110SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.com \
--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).