From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132362-132369 [PATCH] [v2,8/8] net/bonding: add commands
Date: Fri, 06 Oct 2023 19:09:44 -0700 (PDT) [thread overview]
Message-ID: <6520bde8.a70a0220.468f8.983eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/132369
_Functional Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Saturday, October 07 2023 01:34:40
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4dd146e597d81d900140a904e0b3b9feb1b0be6c
132362-132369 --> functional testing pass
Test environment and result as below:
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 XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27846/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-07 2:09 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 2:09 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-07 3:33 dpdklab
2023-10-07 3:28 dpdklab
2023-10-07 3:23 dpdklab
2023-10-07 2:59 dpdklab
2023-10-07 2:58 dpdklab
2023-10-07 2:52 dpdklab
2023-10-07 2:51 dpdklab
2023-10-07 2:47 dpdklab
2023-10-07 2:46 dpdklab
2023-10-07 2:45 dpdklab
2023-10-07 2:44 dpdklab
2023-10-07 2:41 dpdklab
2023-10-07 2:41 dpdklab
2023-10-07 2:40 dpdklab
2023-10-07 2:37 dpdklab
2023-10-07 2:34 dpdklab
2023-10-07 2:34 dpdklab
2023-10-07 2:33 dpdklab
2023-10-07 2:33 dpdklab
2023-10-07 2:28 dpdklab
2023-10-07 2:27 dpdklab
2023-10-07 2:25 dpdklab
2023-10-07 2:24 dpdklab
2023-10-07 2:23 dpdklab
2023-10-07 2:23 dpdklab
2023-10-07 2:22 dpdklab
2023-10-07 2:22 dpdklab
2023-10-07 2:21 dpdklab
2023-10-07 2:18 dpdklab
2023-10-07 2:18 dpdklab
2023-10-07 2:17 dpdklab
2023-10-07 2:15 dpdklab
2023-10-07 2:14 dpdklab
2023-10-07 2:14 dpdklab
2023-10-07 2:13 dpdklab
2023-10-07 2:13 dpdklab
2023-10-07 2:13 dpdklab
2023-10-07 2:12 dpdklab
2023-10-07 2:11 dpdklab
2023-10-07 2:11 dpdklab
2023-10-07 2:10 dpdklab
2023-10-07 2:10 dpdklab
2023-10-07 2:10 dpdklab
2023-10-07 2:09 dpdklab
2023-10-07 2:08 dpdklab
2023-10-07 2:08 dpdklab
2023-10-07 2:07 dpdklab
2023-10-07 2:06 dpdklab
2023-10-07 2:05 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=6520bde8.a70a0220.468f8.983eSMTPIN_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).