From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 2c54ea7a59dfc0a819d3527309c62846fc8853af
Date: Wed, 20 Mar 2024 04:07:21 -0700 (PDT) [thread overview]
Message-ID: <65fac369.920a0220.e87fb.0e9aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-net-intel
2c54ea7a59dfc0a819d3527309c62846fc8853af --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
| CentOS Stream 9 | PASS |
+-----------------+----------------+
| Debian Bullseye | PASS |
+-----------------+----------------+
| Debian 11 (arm) | PASS |
+-----------------+----------------+
| Fedora 37 | PASS |
+-----------------+----------------+
| Fedora 38 | PASS |
+-----------------+----------------+
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
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
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28553/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-03-20 11:07 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 11:07 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-21 23:48 dpdklab
2024-03-21 23:12 dpdklab
2024-03-21 4:53 dpdklab
2024-03-20 12:17 dpdklab
2024-03-20 11:45 dpdklab
2024-03-20 11:27 dpdklab
2024-03-20 11:26 dpdklab
2024-03-20 11:22 dpdklab
2024-03-20 11:20 dpdklab
2024-03-20 11:18 dpdklab
2024-03-20 11:18 dpdklab
2024-03-20 11:15 dpdklab
2024-03-20 11:14 dpdklab
2024-03-20 11:14 dpdklab
2024-03-20 11:14 dpdklab
2024-03-20 11:13 dpdklab
2024-03-20 11:13 dpdklab
2024-03-20 11:11 dpdklab
2024-03-20 11:11 dpdklab
2024-03-20 11:11 dpdklab
2024-03-20 11:11 dpdklab
2024-03-20 11:10 dpdklab
2024-03-20 11:10 dpdklab
2024-03-20 11:09 dpdklab
2024-03-20 11:07 dpdklab
2024-03-20 11:07 dpdklab
2024-03-20 11:07 dpdklab
2024-03-20 11:07 dpdklab
2024-03-20 11:06 dpdklab
2024-03-20 11:06 dpdklab
2024-03-20 11:06 dpdklab
2024-03-20 11:06 dpdklab
2024-03-20 11:06 dpdklab
2024-03-20 11:06 dpdklab
2024-03-20 11:05 dpdklab
2024-03-20 11:05 dpdklab
2024-03-20 11:05 dpdklab
2024-03-20 11:05 dpdklab
2024-03-20 11:05 dpdklab
2024-03-20 11:04 dpdklab
2024-03-20 11:04 dpdklab
2024-03-20 11:04 dpdklab
2024-03-20 11:04 dpdklab
2024-03-20 11:04 dpdklab
2024-03-20 11:04 dpdklab
2024-03-20 11:03 dpdklab
2024-03-20 11:03 dpdklab
2024-03-20 11:03 dpdklab
2024-03-20 11:03 dpdklab
2024-03-20 11:03 dpdklab
2024-03-20 11:02 dpdklab
2024-03-20 11:02 dpdklab
2024-03-20 11:02 dpdklab
2024-03-20 11:02 dpdklab
2024-03-20 11:01 dpdklab
2024-03-20 11:01 dpdklab
2024-03-20 11:01 dpdklab
2024-03-20 11:00 dpdklab
2024-03-20 11:00 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=65fac369.920a0220.e87fb.0e9aSMTPIN_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).