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] 74fce0da4e22931e6382d9345fb7e0ad360426f5
Date: Fri, 3 Feb 2023 18:13:10 -0500 (EST) [thread overview]
Message-ID: <20230203231310.5D857456@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
_Functional Testing PASS_
Branch: dpdk-next-net
74fce0da4e22931e6382d9345fb7e0ad360426f5 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/23150/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-03 23:13 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 23:13 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-05 23:01 dpdklab
2023-02-05 22:40 dpdklab
2023-02-05 20:12 dpdklab
2023-02-05 2:38 dpdklab
2023-02-05 2:38 dpdklab
2023-02-05 2:38 dpdklab
2023-02-05 2:37 dpdklab
2023-02-05 2:37 dpdklab
2023-02-05 2:37 dpdklab
2023-02-05 2:37 dpdklab
2023-02-05 2:37 dpdklab
2023-02-05 2:37 dpdklab
2023-02-05 2:36 dpdklab
2023-02-05 2:36 dpdklab
2023-02-05 2:30 dpdklab
2023-02-05 2:30 dpdklab
2023-02-05 2:30 dpdklab
2023-02-05 2:30 dpdklab
2023-02-05 2:06 dpdklab
2023-02-05 1:50 dpdklab
2023-02-05 1:43 dpdklab
2023-02-05 0:03 dpdklab
2023-02-05 0:02 dpdklab
2023-02-05 0:02 dpdklab
2023-02-05 0:02 dpdklab
2023-02-05 0:01 dpdklab
2023-02-05 0:01 dpdklab
2023-02-05 0:01 dpdklab
2023-02-05 0:01 dpdklab
2023-02-05 0:01 dpdklab
2023-02-05 0:01 dpdklab
2023-02-04 22:14 dpdklab
2023-02-04 0:49 dpdklab
2023-02-03 23:53 dpdklab
2023-02-03 23:08 dpdklab
2023-02-03 23:00 dpdklab
2023-02-03 23:00 dpdklab
2023-02-03 22:58 dpdklab
2023-02-03 22:56 dpdklab
2023-02-03 22:54 dpdklab
2023-02-03 22:54 dpdklab
2023-02-03 22:50 dpdklab
2023-02-03 22:48 dpdklab
2023-02-03 22:48 dpdklab
2023-02-03 22:31 dpdklab
2023-02-03 22:28 dpdklab
2023-02-03 22:20 dpdklab
2023-02-03 22:19 dpdklab
2023-02-03 22:11 dpdklab
2023-02-03 22:11 dpdklab
2023-02-03 22:09 dpdklab
2023-02-03 21:34 dpdklab
2023-02-03 19:50 dpdklab
2023-02-03 19:45 dpdklab
2023-02-03 19:33 dpdklab
2023-02-03 19:31 dpdklab
2023-02-03 19:30 dpdklab
2023-02-03 19:29 dpdklab
2023-02-03 19:28 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=20230203231310.5D857456@noxus.dpdklab.iol.unh.edu \
--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).