From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134952-134954 [PATCH] [v3,3/3] net/hns3: fix incorrect r
Date: Fri, 08 Dec 2023 03:42:31 -0800 (PST) [thread overview]
Message-ID: <65730127.250a0220.2bf8f.6acfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/134954
_Functional Testing PASS_
Submitter: Jie Hai <haijie1@huawei.com>
Date: Friday, December 08 2023 07:44:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f2d5afbb2c05d7647da7ea914887c52115652651
134952-134954 --> functional testing pass
Test environment and result as below:
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/4
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-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
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/4
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28564/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-08 11:42 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 11:42 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-09 0:43 dpdklab
2023-12-08 13:26 dpdklab
2023-12-08 12:53 dpdklab
2023-12-08 12:23 dpdklab
2023-12-08 12:23 dpdklab
2023-12-08 12:21 dpdklab
2023-12-08 12:20 dpdklab
2023-12-08 12:20 dpdklab
2023-12-08 12:20 dpdklab
2023-12-08 12:19 dpdklab
2023-12-08 12:19 dpdklab
2023-12-08 12:13 dpdklab
2023-12-08 12:12 dpdklab
2023-12-08 12:12 dpdklab
2023-12-08 12:12 dpdklab
2023-12-08 12:11 dpdklab
2023-12-08 12:02 dpdklab
2023-12-08 12:02 dpdklab
2023-12-08 12:02 dpdklab
2023-12-08 12:01 dpdklab
2023-12-08 12:01 dpdklab
2023-12-08 12:01 dpdklab
2023-12-08 12:01 dpdklab
2023-12-08 12:01 dpdklab
2023-12-08 12:01 dpdklab
2023-12-08 12:01 dpdklab
2023-12-08 12:01 dpdklab
2023-12-08 12:00 dpdklab
2023-12-08 12:00 dpdklab
2023-12-08 12:00 dpdklab
2023-12-08 12:00 dpdklab
2023-12-08 12:00 dpdklab
2023-12-08 12:00 dpdklab
2023-12-08 12:00 dpdklab
2023-12-08 11:59 dpdklab
2023-12-08 11:59 dpdklab
2023-12-08 11:59 dpdklab
2023-12-08 11:59 dpdklab
2023-12-08 11:59 dpdklab
2023-12-08 11:59 dpdklab
2023-12-08 11:59 dpdklab
2023-12-08 11:58 dpdklab
2023-12-08 11:58 dpdklab
2023-12-08 11:58 dpdklab
2023-12-08 11:58 dpdklab
2023-12-08 11:58 dpdklab
2023-12-08 11:53 dpdklab
2023-12-08 11:53 dpdklab
2023-12-08 11:53 dpdklab
2023-12-08 11:53 dpdklab
2023-12-08 11:53 dpdklab
2023-12-08 11:50 dpdklab
2023-12-08 11:46 dpdklab
2023-12-08 11:46 dpdklab
2023-12-08 11:46 dpdklab
2023-12-08 11:44 dpdklab
2023-12-08 11:44 dpdklab
2023-12-08 11:44 dpdklab
2023-12-08 11:44 dpdklab
2023-12-08 11:37 dpdklab
2023-12-08 11:37 dpdklab
2023-12-08 11:36 dpdklab
2023-12-08 11:20 dpdklab
2023-12-08 11:16 dpdklab
2023-12-08 11:06 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=65730127.250a0220.2bf8f.6acfSMTPIN_ADDED_MISSING@mx.google.com \
--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).