From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131005-131012 [PATCH] [v6,8/8] net/rnp handle device int
Date: Thu, 31 Aug 2023 20:23:48 -0700 (PDT) [thread overview]
Message-ID: <64f15944.a70a0220.72ee.b332SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/131012
_Functional Testing PASS_
Submitter: Wenbo Cao <caowenbo@mucse.com>
Date: Friday, September 01 2023 02:30:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:62774b78a84e9fa5df56d04cffed69bef8c901f1
131005-131012 --> 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
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27499/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-01 3:23 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 3:23 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-01 4:36 dpdklab
2023-09-01 4:14 dpdklab
2023-09-01 3:57 dpdklab
2023-09-01 3:52 dpdklab
2023-09-01 3:48 dpdklab
2023-09-01 3:47 dpdklab
2023-09-01 3:38 dpdklab
2023-09-01 3:38 dpdklab
2023-09-01 3:37 dpdklab
2023-09-01 3:36 dpdklab
2023-09-01 3:34 dpdklab
2023-09-01 3:32 dpdklab
2023-09-01 3:31 dpdklab
2023-09-01 3:31 dpdklab
2023-09-01 3:29 dpdklab
2023-09-01 3:29 dpdklab
2023-09-01 3:28 dpdklab
2023-09-01 3:28 dpdklab
2023-09-01 3:28 dpdklab
2023-09-01 3:28 dpdklab
2023-09-01 3:27 dpdklab
2023-09-01 3:27 dpdklab
2023-09-01 3:27 dpdklab
2023-09-01 3:26 dpdklab
2023-09-01 3:26 dpdklab
2023-09-01 3:25 dpdklab
2023-09-01 3:25 dpdklab
2023-09-01 3:24 dpdklab
2023-09-01 3:24 dpdklab
2023-09-01 3:24 dpdklab
2023-09-01 3:24 dpdklab
2023-09-01 3:22 dpdklab
2023-09-01 3:22 dpdklab
2023-09-01 3:22 dpdklab
2023-09-01 3:22 dpdklab
2023-09-01 3:20 dpdklab
2023-09-01 3:20 dpdklab
2023-09-01 3:20 dpdklab
2023-09-01 3:19 dpdklab
2023-09-01 3:18 dpdklab
2023-09-01 3:18 dpdklab
2023-09-01 3:16 dpdklab
2023-09-01 3:15 dpdklab
2023-09-01 3:14 dpdklab
2023-09-01 3:14 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=64f15944.a70a0220.72ee.b332SMTPIN_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).