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| pw125933 [PATCH] [v3] app/testpmd: txonly multiflow port change support
Date: Tue, 11 Apr 2023 21:53:07 +0000 (UTC) [thread overview]
Message-ID: <20230411215307.5C22560092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/125933
_Functional Testing PASS_
Submitter: Joshua Washington <joshwash@google.com>
Date: Tuesday, April 11 2023 20:24:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:65487b12db83c9ef37526a983c43191cd44dae99
125933 --> functional testing pass
Test environment and result as below:
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/25960/
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-11 21:53 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 21:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-12 15:52 dpdklab
2023-04-12 15:50 dpdklab
2023-04-12 15:49 dpdklab
2023-04-12 15:42 dpdklab
2023-04-12 15:41 dpdklab
2023-04-12 15:36 dpdklab
2023-04-12 15:33 dpdklab
2023-04-12 15:30 dpdklab
2023-04-12 15:29 dpdklab
2023-04-12 15:29 dpdklab
2023-04-12 15:28 dpdklab
2023-04-12 15:21 dpdklab
2023-04-12 15:19 dpdklab
2023-04-12 15:18 dpdklab
2023-04-12 15:17 dpdklab
2023-04-12 15:12 dpdklab
2023-04-12 15:12 dpdklab
2023-04-12 15:09 dpdklab
2023-04-12 15:02 dpdklab
2023-04-12 14:35 dpdklab
2023-04-12 14:30 dpdklab
2023-04-12 14:26 dpdklab
2023-04-12 14:09 dpdklab
2023-04-12 14:05 dpdklab
2023-04-12 14:00 dpdklab
2023-04-12 0:10 dpdklab
2023-04-12 0:09 dpdklab
2023-04-11 23:36 dpdklab
2023-04-11 23:36 dpdklab
2023-04-11 23:11 dpdklab
2023-04-11 22:45 dpdklab
2023-04-11 22:36 dpdklab
2023-04-11 22:28 dpdklab
2023-04-11 22:22 dpdklab
2023-04-11 22:19 dpdklab
2023-04-11 22:16 dpdklab
2023-04-11 22:14 dpdklab
2023-04-11 22:12 dpdklab
2023-04-11 22:10 dpdklab
2023-04-11 22:06 dpdklab
2023-04-11 22:01 dpdklab
2023-04-11 21:55 dpdklab
2023-04-11 21:54 dpdklab
2023-04-11 21:53 dpdklab
2023-04-11 21:52 dpdklab
2023-04-11 21:51 dpdklab
2023-04-11 21:50 dpdklab
2023-04-11 21:48 dpdklab
2023-04-11 21:44 dpdklab
2023-04-11 21:43 dpdklab
2023-04-11 21:38 dpdklab
2023-04-11 21:37 dpdklab
2023-04-11 21:36 dpdklab
2023-04-11 21:36 dpdklab
2023-04-11 21:36 dpdklab
2023-04-11 21:29 dpdklab
[not found] <20230411202430.2817217-1-joshwash@google.com>
2023-04-11 20:17 ` |SUCCESS| pw125933 [PATCH v3] " qemudev
2023-04-11 20:21 ` qemudev
2023-04-11 20:26 ` checkpatch
2023-04-11 21:19 ` 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=20230411215307.5C22560092@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).