From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw153070 [PATCH] [v2] ethdev: add support for flow action
Date: Tue, 22 Apr 2025 08:53:34 -0700 (PDT) [thread overview]
Message-ID: <6807bb7e.050a0220.3914f3.2816SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250422055331.1270825-1-kirankumark@marvell.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/153070
_Testing PASS_
Submitter: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
Date: Tuesday, April 22 2025 05:53:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3829b7150b2bacd8df97134f85ec61bfbdc3f4b1
153070 --> testing pass
Upstream job id: Template-DTS-Pipeline#222589
Test environment and result as below:
+--------------------+----------------------+
| Environment | compressdev_zlib_pmd |
+====================+======================+
| Ubuntu 22.04 (ARM) | PASS |
+--------------------+----------------------+
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33047/
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-04-22 15:53 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250422055331.1270825-1-kirankumark@marvell.com>
2025-04-22 5:18 ` |SUCCESS| pw153070 [PATCH v2] ethdev: add support for flow action pop E-tag qemudev
2025-04-22 5:23 ` qemudev
2025-04-22 5:53 ` checkpatch
2025-04-22 13:50 ` |SUCCESS| pw153070 [PATCH] [v2] ethdev: add support for flow action dpdklab
2025-04-22 13:59 ` dpdklab
2025-04-22 14:10 ` dpdklab
2025-04-22 14:19 ` dpdklab
2025-04-22 14:23 ` dpdklab
2025-04-22 14:25 ` dpdklab
2025-04-22 14:25 ` |WARNING| " dpdklab
2025-04-22 14:28 ` |SUCCESS| " dpdklab
2025-04-22 14:34 ` dpdklab
2025-04-22 14:44 ` dpdklab
2025-04-22 14:49 ` dpdklab
2025-04-22 15:01 ` dpdklab
2025-04-22 15:16 ` |WARNING| " dpdklab
2025-04-22 15:30 ` |SUCCESS| " dpdklab
2025-04-22 15:42 ` dpdklab
2025-04-22 15:45 ` dpdklab
2025-04-22 15:52 ` |PENDING| " dpdklab
2025-04-22 15:53 ` dpdklab
2025-04-22 15:53 ` dpdklab [this message]
2025-04-22 15:54 ` |WARNING| " dpdklab
2025-04-22 15:56 ` |SUCCESS| " dpdklab
2025-04-22 15:58 ` dpdklab
2025-04-22 16:02 ` dpdklab
2025-04-22 16:07 ` dpdklab
2025-04-22 16:12 ` dpdklab
2025-04-22 16:13 ` |PENDING| " dpdklab
2025-04-22 16:21 ` |SUCCESS| " dpdklab
2025-04-22 16:31 ` dpdklab
2025-04-22 16:33 ` |WARNING| " dpdklab
2025-04-22 16:33 ` |PENDING| " dpdklab
2025-04-22 16:57 ` dpdklab
2025-04-22 17:14 ` |SUCCESS| " dpdklab
2025-04-22 17:16 ` |WARNING| " dpdklab
2025-04-22 17:17 ` |PENDING| " dpdklab
2025-04-22 17:18 ` |SUCCESS| " dpdklab
2025-04-22 17:20 ` |PENDING| " dpdklab
2025-04-22 17:32 ` |SUCCESS| " dpdklab
2025-04-22 17:33 ` dpdklab
2025-04-22 17:39 ` |PENDING| " dpdklab
2025-04-22 18:00 ` |SUCCESS| " dpdklab
2025-04-22 18:04 ` dpdklab
2025-04-22 18:14 ` dpdklab
2025-04-22 18:29 ` dpdklab
2025-04-22 18:36 ` dpdklab
2025-04-22 18:37 ` dpdklab
2025-04-22 18:38 ` dpdklab
2025-04-22 18:53 ` dpdklab
2025-04-22 18:55 ` dpdklab
2025-04-22 19:13 ` dpdklab
2025-04-22 19:18 ` dpdklab
2025-04-22 19:44 ` 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=6807bb7e.050a0220.3914f3.2816SMTPIN_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).