From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133482 [PATCH] ethdev: fix flow API support for P4-progr
Date: Fri, 27 Oct 2023 06:46:22 -0700 (PDT) [thread overview]
Message-ID: <653bbf2e.170a0220.381ea.3b13SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/133482
_Functional Testing PASS_
Submitter: Wenjing Qiao <wenjing.qiao@intel.com>
Date: Friday, October 27 2023 09:17:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:656dfad43136ef43f4315ab6ed45b78b68c287a7
133482 --> 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: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
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/4
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28110/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-27 13:46 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 13:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-28 19:14 dpdklab
2023-10-27 15:06 dpdklab
2023-10-27 15:01 dpdklab
2023-10-27 14:32 dpdklab
2023-10-27 14:27 dpdklab
2023-10-27 14:26 dpdklab
2023-10-27 14:14 dpdklab
2023-10-27 14:13 dpdklab
2023-10-27 14:11 dpdklab
2023-10-27 14:11 dpdklab
2023-10-27 14:07 dpdklab
2023-10-27 14:07 dpdklab
2023-10-27 14:07 dpdklab
2023-10-27 14:04 dpdklab
2023-10-27 14:02 dpdklab
2023-10-27 14:01 dpdklab
2023-10-27 14:01 dpdklab
2023-10-27 14:01 dpdklab
2023-10-27 14:00 dpdklab
2023-10-27 13:58 dpdklab
2023-10-27 13:57 dpdklab
2023-10-27 13:57 dpdklab
2023-10-27 13:57 dpdklab
2023-10-27 13:57 dpdklab
2023-10-27 13:56 dpdklab
2023-10-27 13:56 dpdklab
2023-10-27 13:56 dpdklab
2023-10-27 13:56 dpdklab
2023-10-27 13:56 dpdklab
2023-10-27 13:56 dpdklab
2023-10-27 13:55 dpdklab
2023-10-27 13:55 dpdklab
2023-10-27 13:54 dpdklab
2023-10-27 13:54 dpdklab
2023-10-27 13:54 dpdklab
2023-10-27 13:54 dpdklab
2023-10-27 13:54 dpdklab
2023-10-27 13:53 dpdklab
2023-10-27 13:53 dpdklab
2023-10-27 13:49 dpdklab
2023-10-27 13:48 dpdklab
2023-10-27 13:46 dpdklab
2023-10-27 13:45 dpdklab
2023-10-27 13:38 dpdklab
2023-10-27 13:34 dpdklab
2023-10-27 13:33 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=653bbf2e.170a0220.381ea.3b13SMTPIN_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).