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] ea9b0f7277acc931ced3fee4a3ee087a26ee1401
Date: Thu, 18 Apr 2024 00:15:02 -0700 (PDT) [thread overview]
Message-ID: <6620c876.4a0a0220.c5423.4711SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net
ea9b0f7277acc931ced3fee4a3ee087a26ee1401 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28864/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-04-18 7:15 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 7:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-18 11:18 dpdklab
2024-04-18 10:39 dpdklab
2024-04-18 10:09 dpdklab
2024-04-18 10:06 dpdklab
2024-04-18 9:51 dpdklab
2024-04-18 9:45 dpdklab
2024-04-18 9:44 dpdklab
2024-04-18 9:37 dpdklab
2024-04-18 8:29 dpdklab
2024-04-18 8:06 dpdklab
2024-04-18 8:02 dpdklab
2024-04-18 8:02 dpdklab
2024-04-18 8:01 dpdklab
2024-04-18 8:00 dpdklab
2024-04-18 7:58 dpdklab
2024-04-18 7:58 dpdklab
2024-04-18 7:56 dpdklab
2024-04-18 7:56 dpdklab
2024-04-18 7:55 dpdklab
2024-04-18 7:55 dpdklab
2024-04-18 7:44 dpdklab
2024-04-18 7:43 dpdklab
2024-04-18 7:33 dpdklab
2024-04-18 7:32 dpdklab
2024-04-18 7:31 dpdklab
2024-04-18 7:31 dpdklab
2024-04-18 7:31 dpdklab
2024-04-18 7:30 dpdklab
2024-04-18 7:30 dpdklab
2024-04-18 7:30 dpdklab
2024-04-18 7:30 dpdklab
2024-04-18 7:30 dpdklab
2024-04-18 7:30 dpdklab
2024-04-18 7:29 dpdklab
2024-04-18 7:29 dpdklab
2024-04-18 7:28 dpdklab
2024-04-18 7:28 dpdklab
2024-04-18 7:28 dpdklab
2024-04-18 7:28 dpdklab
2024-04-18 7:28 dpdklab
2024-04-18 7:25 dpdklab
2024-04-18 7:24 dpdklab
2024-04-18 7:24 dpdklab
2024-04-18 7:24 dpdklab
2024-04-18 7:23 dpdklab
2024-04-18 7:23 dpdklab
2024-04-18 7:23 dpdklab
2024-04-18 7:22 dpdklab
2024-04-18 7:22 dpdklab
2024-04-18 7:22 dpdklab
2024-04-18 7:22 dpdklab
2024-04-18 7:21 dpdklab
2024-04-18 7:21 dpdklab
2024-04-18 7:20 dpdklab
2024-04-18 7:20 dpdklab
2024-04-18 7:19 dpdklab
2024-04-18 7:19 dpdklab
2024-04-18 7:19 dpdklab
2024-04-18 7:18 dpdklab
2024-04-18 7:18 dpdklab
2024-04-18 7:18 dpdklab
2024-04-18 7:18 dpdklab
2024-04-18 7:17 dpdklab
2024-04-18 7:15 dpdklab
2024-04-18 7:15 dpdklab
2024-04-18 7:15 dpdklab
2024-04-18 7:14 dpdklab
2024-04-18 7:14 dpdklab
2024-04-18 7:14 dpdklab
2024-04-18 7:13 dpdklab
2024-04-18 7:13 dpdklab
2024-04-18 7:13 dpdklab
2024-04-18 7:12 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=6620c876.4a0a0220.c5423.4711SMTPIN_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).