From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134086 [PATCH] app/test: fix retest link bonding fail
Date: Tue, 14 Nov 2023 06:13:31 -0800 (PST) [thread overview]
Message-ID: <6553808b.050a0220.160be.a461SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/134086
_Functional Testing PASS_
Submitter: Jie Hai <haijie1@huawei.com>
Date: Friday, November 10 2023 09:53:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:de0ec3c2458e3e2ce53e504c4ba92a36fcc78ef3
134086 --> 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: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28326/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-14 14:13 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 14:13 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-14 13:28 dpdklab
2023-11-10 19:01 dpdklab
2023-11-10 14:52 dpdklab
2023-11-10 13:22 dpdklab
2023-11-10 12:38 dpdklab
2023-11-10 12:35 dpdklab
2023-11-10 12:32 dpdklab
2023-11-10 12:32 dpdklab
2023-11-10 12:31 dpdklab
2023-11-10 12:31 dpdklab
2023-11-10 12:31 dpdklab
2023-11-10 12:31 dpdklab
2023-11-10 12:30 dpdklab
2023-11-10 12:30 dpdklab
2023-11-10 12:29 dpdklab
2023-11-10 12:27 dpdklab
2023-11-10 12:26 dpdklab
2023-11-10 12:25 dpdklab
2023-11-10 12:23 dpdklab
2023-11-10 12:22 dpdklab
2023-11-10 12:21 dpdklab
2023-11-10 12:16 dpdklab
2023-11-10 12:15 dpdklab
2023-11-10 12:14 dpdklab
2023-11-10 12:14 dpdklab
2023-11-10 12:03 dpdklab
2023-11-10 12:02 dpdklab
2023-11-10 12:01 dpdklab
2023-11-10 12:01 dpdklab
2023-11-10 12:01 dpdklab
2023-11-10 12:01 dpdklab
2023-11-10 12:00 dpdklab
2023-11-10 12:00 dpdklab
2023-11-10 12:00 dpdklab
2023-11-10 11:59 dpdklab
2023-11-10 11:58 dpdklab
2023-11-10 11:58 dpdklab
2023-11-10 11:57 dpdklab
2023-11-10 11:57 dpdklab
2023-11-10 11:57 dpdklab
2023-11-10 11:56 dpdklab
2023-11-10 11:56 dpdklab
2023-11-10 11:56 dpdklab
2023-11-10 11:56 dpdklab
2023-11-10 11:55 dpdklab
2023-11-10 11:51 dpdklab
2023-11-10 11:21 dpdklab
2023-11-10 11:21 dpdklab
2023-11-10 11:21 dpdklab
2023-11-10 11:21 dpdklab
2023-11-10 11:16 dpdklab
2023-11-10 11:16 dpdklab
2023-11-10 11:15 dpdklab
2023-11-10 11:13 dpdklab
2023-11-10 11:12 dpdklab
2023-11-10 11:10 dpdklab
[not found] <20231110095302.2469090-1-haijie1@huawei.com>
2023-11-10 9:37 ` qemudev
2023-11-10 9:41 ` qemudev
2023-11-10 9:57 ` checkpatch
2023-11-10 10:59 ` 0-day Robot
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=6553808b.050a0220.160be.a461SMTPIN_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).