From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152321 [PATCH] net/mlx5: fix mark flow action validation
Date: Tue, 11 Mar 2025 08:00:34 -0700 (PDT) [thread overview]
Message-ID: <67d05012.170a0220.1c9f73.9321SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250311124635.1262066-1-getelson@nvidia.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152321
_Functional Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Tuesday, March 11 2025 12:46:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6a2610c2f4b8ad7b3cec850bad14c4af8840654f
152321 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#217189
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
NIC: Intel Corporation QAT 8970 0 Mbps
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | PASS |
+----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32796/
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:[~2025-03-11 15:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250311124635.1262066-1-getelson@nvidia.com>
2025-03-11 12:13 ` |SUCCESS| pw152321 [PATCH] net/mlx5: fix mark flow action validation in FDB mode qemudev
2025-03-11 12:17 ` qemudev
2025-03-11 12:47 ` checkpatch
2025-03-11 14:03 ` 0-day Robot
2025-03-11 14:41 ` |SUCCESS| pw152321 [PATCH] net/mlx5: fix mark flow action validation dpdklab
2025-03-11 14:51 ` dpdklab
2025-03-11 15:00 ` dpdklab [this message]
2025-03-11 15:02 ` dpdklab
2025-03-11 15:04 ` dpdklab
2025-03-11 15:13 ` dpdklab
2025-03-11 15:16 ` dpdklab
2025-03-11 15:16 ` dpdklab
2025-03-11 15:27 ` dpdklab
2025-03-11 15:39 ` |PENDING| " dpdklab
2025-03-11 15:53 ` dpdklab
2025-03-11 16:21 ` dpdklab
2025-03-11 16:28 ` |SUCCESS| " dpdklab
2025-03-11 16:40 ` |PENDING| " dpdklab
2025-03-11 16:48 ` |SUCCESS| " dpdklab
2025-03-11 16:48 ` dpdklab
2025-03-11 17:04 ` dpdklab
2025-03-11 17:13 ` dpdklab
2025-03-11 17:46 ` dpdklab
2025-03-11 18:19 ` dpdklab
2025-03-11 18:19 ` dpdklab
2025-03-11 18:21 ` dpdklab
2025-03-11 18:50 ` dpdklab
2025-03-11 20:14 ` 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=67d05012.170a0220.1c9f73.9321SMTPIN_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).