From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137374-137396 [PATCH] [v4,23/23] net/cnxk: other flow op
Date: Thu, 29 Feb 2024 08:44:14 -0800 (PST) [thread overview]
Message-ID: <65e0b45e.c80a0220.b906e.3611SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227191550.137687-24-hkalra@marvell.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137396
_Functional Testing PASS_
Submitter: Harman Kalra <hkalra@marvell.com>
Date: Tuesday, February 27 2024 19:15:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ab5b7cd5a0b563e6d49be6c8beaad1f39c581a5c
137374-137396 --> 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/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
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 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/29301/
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-02-29 16:44 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240227191550.137687-24-hkalra@marvell.com>
2024-02-27 19:05 ` |SUCCESS| pw137374-137396 [PATCH v4 23/23] net/cnxk: other flow operations qemudev
2024-02-27 19:09 ` qemudev
2024-02-27 19:21 ` |WARNING| pw137396 " checkpatch
2024-02-28 2:25 ` |SUCCESS| pw137374-137396 [PATCH] [v4,23/23] net/cnxk: other flow op dpdklab
2024-02-28 2:28 ` dpdklab
2024-02-28 2:29 ` dpdklab
2024-02-28 2:33 ` dpdklab
2024-02-28 2:41 ` dpdklab
2024-02-28 2:41 ` dpdklab
2024-02-28 2:42 ` dpdklab
2024-02-28 2:43 ` dpdklab
2024-02-28 2:44 ` dpdklab
2024-02-28 2:45 ` dpdklab
2024-02-28 2:46 ` dpdklab
2024-02-28 2:56 ` dpdklab
2024-02-28 2:58 ` dpdklab
2024-02-28 2:59 ` dpdklab
2024-02-28 3:41 ` dpdklab
2024-02-28 3:49 ` dpdklab
2024-02-28 4:03 ` dpdklab
2024-02-28 4:06 ` dpdklab
2024-02-28 4:06 ` dpdklab
2024-02-28 4:06 ` dpdklab
2024-02-28 4:06 ` dpdklab
2024-02-28 4:08 ` dpdklab
2024-02-28 4:08 ` dpdklab
2024-02-28 4:09 ` dpdklab
2024-02-28 4:09 ` dpdklab
2024-02-28 4:09 ` dpdklab
2024-02-28 4:09 ` dpdklab
2024-02-28 4:10 ` dpdklab
2024-02-28 4:10 ` dpdklab
2024-02-28 4:13 ` dpdklab
2024-02-28 4:19 ` dpdklab
2024-02-28 4:20 ` dpdklab
2024-02-28 4:20 ` dpdklab
2024-02-28 4:22 ` dpdklab
2024-02-28 4:22 ` dpdklab
2024-02-28 4:23 ` dpdklab
2024-02-28 4:26 ` dpdklab
2024-02-28 4:28 ` dpdklab
2024-02-28 4:30 ` dpdklab
2024-02-28 5:11 ` dpdklab
2024-02-28 5:11 ` dpdklab
2024-02-28 6:20 ` dpdklab
2024-02-28 6:30 ` dpdklab
2024-02-28 6:45 ` dpdklab
2024-02-28 6:45 ` dpdklab
2024-02-28 6:46 ` dpdklab
2024-02-28 6:46 ` dpdklab
2024-02-28 6:48 ` dpdklab
2024-02-28 6:54 ` dpdklab
2024-02-28 7:00 ` dpdklab
2024-02-28 7:01 ` dpdklab
2024-02-28 7:03 ` dpdklab
2024-02-28 7:09 ` dpdklab
2024-02-28 7:20 ` dpdklab
2024-02-28 7:22 ` dpdklab
2024-02-28 10:58 ` dpdklab
2024-02-28 13:50 ` dpdklab
2024-02-28 14:34 ` dpdklab
2024-02-28 22:12 ` dpdklab
2024-02-29 16:42 ` dpdklab
2024-02-29 16:44 ` dpdklab [this message]
2024-02-29 16:47 ` dpdklab
2024-02-29 17:02 ` dpdklab
2024-02-29 17:32 ` dpdklab
2024-02-29 19:21 ` dpdklab
2024-02-29 19:52 ` 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=65e0b45e.c80a0220.b906e.3611SMTPIN_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).