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] 418f86c426f23ad3ffd397e69d19e8d6b5577e67
Date: Wed, 22 Feb 2023 14:26:05 -0500 (EST) [thread overview]
Message-ID: <20230222192605.8DB6AB0B3@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 605 bytes --]
_Functional Testing PASS_
Branch: dpdk-next-net
418f86c426f23ad3ffd397e69d19e8d6b5577e67 --> functional testing pass
Test environment and result as below:
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/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/23462/
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-22 19:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 19:26 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 4:12 dpdklab
2023-02-22 23:58 dpdklab
2023-02-22 23:58 dpdklab
2023-02-22 23:47 dpdklab
2023-02-22 23:42 dpdklab
2023-02-22 23:33 dpdklab
2023-02-22 23:31 dpdklab
2023-02-22 23:22 dpdklab
2023-02-22 23:18 dpdklab
2023-02-22 23:14 dpdklab
2023-02-22 23:12 dpdklab
2023-02-22 23:10 dpdklab
2023-02-22 22:50 dpdklab
2023-02-22 19:51 dpdklab
2023-02-22 19:47 dpdklab
2023-02-22 19:38 dpdklab
2023-02-22 19:37 dpdklab
2023-02-22 19:34 dpdklab
2023-02-22 19:32 dpdklab
2023-02-22 19:31 dpdklab
2023-02-22 19:29 dpdklab
2023-02-22 19:21 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=20230222192605.8DB6AB0B3@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).