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| pw126417 [PATCH] [v5] app/testpmd: txonly multiflow port change support
Date: Tue, 25 Apr 2023 00:09:54 -0700 (PDT) [thread overview]
Message-ID: <64477cc2.4a0a0220.934af.d08aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/126417
_Functional Testing PASS_
Submitter: Joshua Washington <joshwash@google.com>
Date: Friday, April 21 2023 23:20:22
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70cc4e1fed665712e68f2f45d98dda4abc6accda
126417 --> functional testing pass
Test environment and result as below:
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/2
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26090/
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-25 7:09 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 7:09 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-25 13:56 dpdklab
2023-04-25 13:53 dpdklab
2023-04-25 8:04 dpdklab
2023-04-25 7:52 dpdklab
2023-04-25 7:52 dpdklab
2023-04-25 7:44 dpdklab
2023-04-25 7:44 dpdklab
2023-04-25 7:42 dpdklab
2023-04-25 7:42 dpdklab
2023-04-25 7:41 dpdklab
2023-04-25 7:40 dpdklab
2023-04-25 7:40 dpdklab
2023-04-25 7:39 dpdklab
2023-04-25 7:39 dpdklab
2023-04-25 7:33 dpdklab
2023-04-25 7:33 dpdklab
2023-04-25 7:32 dpdklab
2023-04-25 7:27 dpdklab
2023-04-25 7:24 dpdklab
2023-04-25 7:17 dpdklab
2023-04-25 7:11 dpdklab
2023-04-25 7:11 dpdklab
2023-04-25 7:09 dpdklab
2023-04-25 7:06 dpdklab
2023-04-25 7:06 dpdklab
2023-04-25 7:04 dpdklab
2023-04-25 7:04 dpdklab
2023-04-22 4:51 dpdklab
2023-04-22 4:17 dpdklab
2023-04-22 3:45 dpdklab
2023-04-22 2:25 dpdklab
2023-04-22 2:23 dpdklab
2023-04-22 2:21 dpdklab
2023-04-22 2:15 dpdklab
2023-04-22 2:15 dpdklab
2023-04-22 2:13 dpdklab
2023-04-22 2:02 dpdklab
2023-04-22 1:57 dpdklab
2023-04-22 1:47 dpdklab
2023-04-22 1:24 dpdklab
2023-04-22 1:17 dpdklab
2023-04-22 1:13 dpdklab
2023-04-22 1:10 dpdklab
2023-04-22 1:09 dpdklab
2023-04-22 1:09 dpdklab
2023-04-22 1:04 dpdklab
2023-04-22 1:03 dpdklab
2023-04-22 1:02 dpdklab
2023-04-22 1:01 dpdklab
2023-04-22 0:57 dpdklab
2023-04-22 0:55 dpdklab
2023-04-22 0:54 dpdklab
[not found] <20230421232022.342081-1-joshwash@google.com>
2023-04-21 23:09 ` |SUCCESS| pw126417 [PATCH v5] " qemudev
2023-04-21 23:13 ` qemudev
2023-04-21 23:21 ` checkpatch
2023-04-22 0: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=64477cc2.4a0a0220.934af.d08aSMTPIN_ADDED_MISSING@mx.google.com \
--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).