From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152192-152193 [PATCH] [2/2] net/mlx5: fix non template f
Date: Mon, 03 Mar 2025 18:13:36 -0800 (PST) [thread overview]
Message-ID: <67c661d0.050a0220.29b3be.fd21SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250303133450.71626-2-mkashani@nvidia.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152193
_Functional Testing PASS_
Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Monday, March 03 2025 13:34:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cf35973540c8bb4ca5c7d105985a65a3602e5475
152192-152193 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#215826
Test environment and result as below:
Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc
Aggregate Results by Test Suite
+----------------+--------+
| Test Suite | Result |
+================+========+
| cmdline | PASS |
+----------------+--------+
| rxtx_callbacks | PASS |
+----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32732/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2025-03-04 2:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250303133450.71626-2-mkashani@nvidia.com>
2025-03-03 13:04 ` |SUCCESS| pw152192-152193 [PATCH 2/2] net/mlx5: fix non template flow validation on create qemudev
2025-03-03 13:09 ` qemudev
2025-03-03 13:36 ` |SUCCESS| pw152193 " checkpatch
2025-03-03 14:44 ` 0-day Robot
2025-03-03 16:17 ` |SUCCESS| pw152192-152193 [PATCH] [2/2] net/mlx5: fix non template f dpdklab
2025-03-03 16:31 ` dpdklab
2025-03-03 16:42 ` dpdklab
2025-03-03 16:51 ` |PENDING| " dpdklab
2025-03-03 16:57 ` |SUCCESS| " dpdklab
2025-03-03 17:01 ` dpdklab
2025-03-03 17:04 ` |PENDING| " dpdklab
2025-03-03 17:07 ` |SUCCESS| " dpdklab
2025-03-03 17:10 ` dpdklab
2025-03-03 17:15 ` dpdklab
2025-03-03 17:19 ` |PENDING| " dpdklab
2025-03-03 17:30 ` |SUCCESS| " dpdklab
2025-03-03 17:34 ` |PENDING| " dpdklab
2025-03-03 17:40 ` |SUCCESS| " dpdklab
2025-03-03 17:45 ` dpdklab
2025-03-03 17:54 ` |PENDING| " dpdklab
2025-03-03 18:51 ` |SUCCESS| " dpdklab
2025-03-03 19:01 ` dpdklab
2025-03-03 19:02 ` dpdklab
2025-03-03 19:21 ` dpdklab
2025-03-03 19:32 ` dpdklab
2025-03-03 19:33 ` dpdklab
2025-03-04 2:13 ` dpdklab [this message]
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=67c661d0.050a0220.29b3be.fd21SMTPIN_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).