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] ae59c6a42ee4f49409997765ae64502944e0ac33
Date: Fri, 19 Apr 2024 01:19:34 -0700 (PDT) [thread overview]
Message-ID: <66222916.0d0a0220.23a18.b60bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-net
ae59c6a42ee4f49409997765ae64502944e0ac33 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28882/
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-19 8:19 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 8:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-19 12:40 dpdklab
2024-04-19 12:31 dpdklab
2024-04-19 12:15 dpdklab
2024-04-19 12:07 dpdklab
2024-04-19 11:56 dpdklab
2024-04-19 11:52 dpdklab
2024-04-19 11:50 dpdklab
2024-04-19 11:48 dpdklab
2024-04-19 10:42 dpdklab
2024-04-19 10:15 dpdklab
2024-04-19 10:13 dpdklab
2024-04-19 10:12 dpdklab
2024-04-19 10:09 dpdklab
2024-04-19 10:09 dpdklab
2024-04-19 10:08 dpdklab
2024-04-19 10:07 dpdklab
2024-04-19 10:07 dpdklab
2024-04-19 10:07 dpdklab
2024-04-19 10:07 dpdklab
2024-04-19 10:06 dpdklab
2024-04-19 9:59 dpdklab
2024-04-19 9:59 dpdklab
2024-04-19 9:59 dpdklab
2024-04-19 9:59 dpdklab
2024-04-19 9:59 dpdklab
2024-04-19 9:59 dpdklab
2024-04-19 9:59 dpdklab
2024-04-19 9:59 dpdklab
2024-04-19 9:59 dpdklab
2024-04-19 9:59 dpdklab
2024-04-19 9:57 dpdklab
2024-04-19 9:57 dpdklab
2024-04-19 9:57 dpdklab
2024-04-19 9:57 dpdklab
2024-04-19 9:57 dpdklab
2024-04-19 9:57 dpdklab
2024-04-19 9:56 dpdklab
2024-04-19 9:52 dpdklab
2024-04-19 9:51 dpdklab
2024-04-19 9:51 dpdklab
2024-04-19 9:51 dpdklab
2024-04-19 9:49 dpdklab
2024-04-19 9:49 dpdklab
2024-04-19 9:49 dpdklab
2024-04-19 9:45 dpdklab
2024-04-19 9:44 dpdklab
2024-04-19 9:44 dpdklab
2024-04-19 9:43 dpdklab
2024-04-19 9:43 dpdklab
2024-04-19 9:42 dpdklab
2024-04-19 9:41 dpdklab
2024-04-19 9:40 dpdklab
2024-04-19 9:36 dpdklab
2024-04-19 9:33 dpdklab
2024-04-19 8:11 dpdklab
2024-04-19 8:10 dpdklab
2024-04-19 8:10 dpdklab
2024-04-19 8:03 dpdklab
2024-04-19 7:56 dpdklab
2024-04-19 7:50 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=66222916.0d0a0220.23a18.b60bSMTPIN_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).