From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw93275-93274 [PATCH] [6/6] net/hns3: fix link speed when VF device is down
Date: Tue, 18 May 2021 16:21:52 -0400 (EDT) [thread overview]
Message-ID: <20210518202152.2C5AA4B0@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/93274
_Functional Testing PASS_
Submitter: Min Hu (Connor) <humin29@huawei.com>
Date: Saturday, May 15 2021 00:52:38
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7989b7e7da9be588563c809264c9347a35319969
93275-93274 --> functional testing pass
Test environment and result as below:
Ubuntu 18.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/5
Ubuntu 18.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/5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/17108/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-05-18 20:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 20:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-18 23:05 dpdklab
2021-05-18 20:47 dpdklab
2021-05-18 20:06 dpdklab
2021-05-17 7:34 dpdklab
2021-05-17 7:22 dpdklab
2021-05-17 6:41 dpdklab
2021-05-17 6:00 dpdklab
2021-05-17 5:48 dpdklab
2021-05-15 1:37 dpdklab
2021-05-15 1:35 dpdklab
2021-05-15 1:32 dpdklab
2021-05-15 1:25 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=20210518202152.2C5AA4B0@noxus.dpdklab.iol.unh.edu \
--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).