From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125970 [PATCH] [v4] app/testpmd: txonly multiflow port change support
Date: Wed, 12 Apr 2023 21:35:17 +0000 (UTC) [thread overview]
Message-ID: <20230412213517.F069B60095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/125970
_Functional Testing PASS_
Submitter: Joshua Washington <joshwash@google.com>
Date: Wednesday, April 12 2023 18:16:19
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
125970 --> functional testing pass
Test environment and result as below:
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/25974/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-12 21:35 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 21:35 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-13 3:45 dpdklab
2023-04-13 3:44 dpdklab
2023-04-13 3:15 dpdklab
2023-04-13 3:15 dpdklab
2023-04-13 1:40 dpdklab
2023-04-13 1:35 dpdklab
2023-04-13 1:30 dpdklab
2023-04-13 1:15 dpdklab
2023-04-13 1:11 dpdklab
2023-04-13 0:55 dpdklab
2023-04-13 0:26 dpdklab
2023-04-13 0:25 dpdklab
2023-04-13 0:11 dpdklab
2023-04-13 0:07 dpdklab
2023-04-13 0:07 dpdklab
2023-04-13 0:01 dpdklab
2023-04-12 23:59 dpdklab
2023-04-12 23:58 dpdklab
2023-04-12 23:57 dpdklab
2023-04-12 23:54 dpdklab
2023-04-12 23:54 dpdklab
2023-04-12 23:42 dpdklab
2023-04-12 23:40 dpdklab
2023-04-12 23:40 dpdklab
2023-04-12 23:38 dpdklab
2023-04-12 23:38 dpdklab
2023-04-12 23:37 dpdklab
2023-04-12 23:34 dpdklab
2023-04-12 23:34 dpdklab
2023-04-12 23:32 dpdklab
2023-04-12 23:32 dpdklab
2023-04-12 23:31 dpdklab
2023-04-12 23:27 dpdklab
2023-04-12 23:25 dpdklab
2023-04-12 22:46 dpdklab
2023-04-12 22:20 dpdklab
2023-04-12 22:17 dpdklab
2023-04-12 22:14 dpdklab
2023-04-12 22:10 dpdklab
2023-04-12 22:07 dpdklab
2023-04-12 22:02 dpdklab
2023-04-12 22:02 dpdklab
2023-04-12 22:00 dpdklab
2023-04-12 21:59 dpdklab
2023-04-12 21:57 dpdklab
2023-04-12 21:54 dpdklab
2023-04-12 21:46 dpdklab
2023-04-12 21:44 dpdklab
2023-04-12 21:35 dpdklab
2023-04-12 21:28 dpdklab
2023-04-12 21:27 dpdklab
2023-04-12 21:27 dpdklab
2023-04-12 21:26 dpdklab
2023-04-12 21:25 dpdklab
2023-04-12 21:22 dpdklab
2023-04-12 21:20 dpdklab
[not found] <20230412181619.496342-1-joshwash@google.com>
2023-04-12 18:07 ` |SUCCESS| pw125970 [PATCH v4] " qemudev
2023-04-12 18:11 ` qemudev
2023-04-12 18:17 ` checkpatch
2023-04-12 19:18 ` 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=20230412213517.F069B60095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).