From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138129 [PATCH] [v2] net/netvsc: fix number Tx queues > R
Date: Fri, 08 Mar 2024 10:50:06 -0800 (PST) [thread overview]
Message-ID: <65eb5dde.050a0220.88858.a332SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <DU0PR83MB05321DB2ADBEDAE7687773DF97272@DU0PR83MB0532.EURPRD83.prod.outlook.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138129
_Functional Testing PASS_
Submitter: Alan Elder <alan.elder@microsoft.com>
Date: Friday, March 08 2024 18:09:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a86f381b826660e88794754c41d3aec79ce9b87c
138129 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-82
Compiler: gcc 11.4.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/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29481/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-08 18:50 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DU0PR83MB05321DB2ADBEDAE7687773DF97272@DU0PR83MB0532.EURPRD83.prod.outlook.com>
2024-03-08 18:04 ` |SUCCESS| pw138129 [PATCH v2] net/netvsc: fix number Tx queues > Rx queues qemudev
2024-03-08 18:09 ` qemudev
2024-03-08 18:10 ` checkpatch
2024-03-08 18:44 ` |SUCCESS| pw138129 [PATCH] [v2] net/netvsc: fix number Tx queues > R dpdklab
2024-03-08 18:45 ` dpdklab
2024-03-08 18:45 ` dpdklab
2024-03-08 18:46 ` dpdklab
2024-03-08 18:46 ` dpdklab
2024-03-08 18:46 ` dpdklab
2024-03-08 18:46 ` dpdklab
2024-03-08 18:47 ` dpdklab
2024-03-08 18:47 ` dpdklab
2024-03-08 18:48 ` dpdklab
2024-03-08 18:48 ` dpdklab
2024-03-08 18:48 ` dpdklab
2024-03-08 18:49 ` dpdklab
2024-03-08 18:49 ` dpdklab
2024-03-08 18:49 ` dpdklab
2024-03-08 18:49 ` dpdklab
2024-03-08 18:50 ` dpdklab [this message]
2024-03-08 18:50 ` dpdklab
2024-03-08 18:51 ` dpdklab
2024-03-08 18:51 ` dpdklab
2024-03-08 18:52 ` dpdklab
2024-03-08 18:52 ` dpdklab
2024-03-08 18:52 ` dpdklab
2024-03-08 18:53 ` dpdklab
2024-03-08 18:53 ` dpdklab
2024-03-08 18:53 ` dpdklab
2024-03-08 18:53 ` dpdklab
2024-03-08 18:53 ` dpdklab
2024-03-08 18:54 ` dpdklab
2024-03-08 18:54 ` dpdklab
2024-03-08 18:54 ` dpdklab
2024-03-08 18:54 ` dpdklab
2024-03-08 18:54 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:55 ` dpdklab
2024-03-08 18:56 ` dpdklab
2024-03-08 18:56 ` dpdklab
2024-03-08 18:56 ` dpdklab
2024-03-08 18:56 ` dpdklab
2024-03-08 18:56 ` dpdklab
2024-03-08 18:57 ` dpdklab
2024-03-08 18:57 ` dpdklab
2024-03-08 18:57 ` dpdklab
2024-03-08 18:57 ` dpdklab
2024-03-08 18:57 ` dpdklab
2024-03-08 18:57 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:58 ` dpdklab
2024-03-08 18:59 ` dpdklab
2024-03-08 18:59 ` dpdklab
2024-03-08 19:00 ` dpdklab
2024-03-08 19:02 ` dpdklab
2024-03-08 19:03 ` dpdklab
2024-03-08 19:03 ` |SUCCESS| pw138129 [PATCH v2] net/netvsc: fix number Tx queues > Rx queues 0-day Robot
2024-03-08 19:04 ` |SUCCESS| pw138129 [PATCH] [v2] net/netvsc: fix number Tx queues > R dpdklab
2024-03-08 19:07 ` dpdklab
2024-03-08 19:14 ` dpdklab
2024-03-08 19:27 ` dpdklab
2024-03-08 20:09 ` dpdklab
2024-03-13 10:37 ` dpdklab
2024-03-13 11:00 ` 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=65eb5dde.050a0220.88858.a332SMTPIN_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).