From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137815-137837 [PATCH] [v6,23/23] net/cnxk: other flow op
Date: Sun, 03 Mar 2024 10:36:57 -0800 (PST) [thread overview]
Message-ID: <65e4c349.050a0220.435f5.b2f7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240303173833.100039-24-hkalra@marvell.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137837
_Functional Testing PASS_
Submitter: Harman Kalra <hkalra@marvell.com>
Date: Sunday, March 03 2024 17:38:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a3d538b3a48d545abe19e9a616fe3b8422275c8d
137815-137837 --> 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/3
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/3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29393/
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-03 18:36 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240303173833.100039-24-hkalra@marvell.com>
2024-03-03 17:19 ` |SUCCESS| pw137815-137837 [PATCH v6 23/23] net/cnxk: other flow operations qemudev
2024-03-03 17:24 ` qemudev
2024-03-03 17:41 ` |WARNING| pw137837 " checkpatch
2024-03-03 18:15 ` |SUCCESS| pw137815-137837 [PATCH] [v6,23/23] net/cnxk: other flow op dpdklab
2024-03-03 18:15 ` dpdklab
2024-03-03 18:16 ` dpdklab
2024-03-03 18:16 ` dpdklab
2024-03-03 18:16 ` dpdklab
2024-03-03 18:16 ` dpdklab
2024-03-03 18:19 ` dpdklab
2024-03-03 18:19 ` dpdklab
2024-03-03 18:20 ` dpdklab
2024-03-03 18:20 ` dpdklab
2024-03-03 18:21 ` dpdklab
2024-03-03 18:21 ` dpdklab
2024-03-03 18:22 ` dpdklab
2024-03-03 18:22 ` dpdklab
2024-03-03 18:23 ` dpdklab
2024-03-03 18:25 ` dpdklab
2024-03-03 18:25 ` dpdklab
2024-03-03 18:26 ` dpdklab
2024-03-03 18:28 ` dpdklab
2024-03-03 18:36 ` dpdklab
2024-03-03 18:36 ` dpdklab
2024-03-03 18:36 ` dpdklab
2024-03-03 18:36 ` dpdklab
2024-03-03 18:36 ` dpdklab [this message]
2024-03-03 18:37 ` dpdklab
2024-03-03 18:37 ` dpdklab
2024-03-03 18:38 ` dpdklab
2024-03-03 18:39 ` dpdklab
2024-03-03 18:39 ` dpdklab
2024-03-03 18:39 ` dpdklab
2024-03-03 18:40 ` dpdklab
2024-03-03 18:41 ` dpdklab
2024-03-03 18:41 ` dpdklab
2024-03-03 18:42 ` dpdklab
2024-03-03 18:47 ` dpdklab
2024-03-03 18:48 ` dpdklab
2024-03-03 18:48 ` dpdklab
2024-03-03 18:48 ` dpdklab
2024-03-03 18:49 ` dpdklab
2024-03-03 18:49 ` dpdklab
2024-03-03 18:50 ` dpdklab
2024-03-03 18:55 ` dpdklab
2024-03-03 18:56 ` dpdklab
2024-03-03 18:56 ` dpdklab
2024-03-03 18:57 ` dpdklab
2024-03-03 18:57 ` dpdklab
2024-03-03 18:58 ` dpdklab
2024-03-03 18:58 ` dpdklab
2024-03-03 18:59 ` dpdklab
2024-03-03 18:59 ` dpdklab
2024-03-03 18:59 ` dpdklab
2024-03-03 19:00 ` dpdklab
2024-03-03 19:00 ` dpdklab
2024-03-03 19:01 ` dpdklab
2024-03-03 19:03 ` dpdklab
2024-03-03 19:03 ` dpdklab
2024-03-03 19:04 ` dpdklab
2024-03-03 19:06 ` dpdklab
2024-03-03 19:08 ` dpdklab
2024-03-03 19:09 ` dpdklab
2024-03-03 19:09 ` dpdklab
2024-03-03 19:12 ` dpdklab
2024-03-03 19:12 ` dpdklab
2024-03-03 19:17 ` dpdklab
2024-03-03 19:26 ` dpdklab
2024-03-03 19:35 ` dpdklab
2024-03-03 19:38 ` dpdklab
2024-03-03 19:52 ` dpdklab
2024-03-03 20:46 ` dpdklab
2024-03-07 6:38 ` dpdklab
2024-03-07 7:05 ` dpdklab
2024-03-07 8:05 ` 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=65e4c349.050a0220.435f5.b2f7SMTPIN_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).