From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] 27d0bd43801528ac9dffd2e6119ad4733c7baa61
Date: Tue, 31 Jan 2023 15:36:17 -0500 (EST) [thread overview]
Message-ID: <20230131203617.3D422B0B3@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
_Functional Testing PASS_
Branch: dpdk-next-net
27d0bd43801528ac9dffd2e6119ad4733c7baa61 --> 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-135-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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/23087/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-01-31 20:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 20:36 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-01 22:55 dpdklab
2023-02-01 21:48 dpdklab
2023-02-01 13:02 dpdklab
2023-02-01 13:01 dpdklab
2023-02-01 13:01 dpdklab
2023-02-01 13:01 dpdklab
2023-02-01 13:01 dpdklab
2023-02-01 13:01 dpdklab
2023-02-01 13:01 dpdklab
2023-02-01 12:59 dpdklab
2023-02-01 12:59 dpdklab
2023-02-01 12:58 dpdklab
2023-02-01 12:02 dpdklab
2023-02-01 0:05 dpdklab
2023-01-31 23:32 dpdklab
2023-01-31 23:10 dpdklab
2023-01-31 22:40 dpdklab
2023-01-31 22:27 dpdklab
2023-01-31 20:27 dpdklab
2023-01-31 20:08 dpdklab
2023-01-31 19:35 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=20230131203617.3D422B0B3@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--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).