From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152516-152517 [PATCH] [2/2] common/cnxk: defragment MCAM
Date: Fri, 21 Mar 2025 07:14:16 -0700 (PDT) [thread overview]
Message-ID: <67dd7438.050a0220.2e305f.4112SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250321094820.3311252-2-psatheesh@marvell.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/152517
_Testing PASS_
Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Friday, March 21 2025 09:48:20
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5f37ee9c859f3ce08ca4364f1d8c0e70ec33ac83
152516-152517 --> testing pass
Upstream job id: Template-DTS-Pipeline#218566
Test environment and result as below:
+--------------------+----------------------+
| Environment | compressdev_zlib_pmd |
+====================+======================+
| Ubuntu 22.04 (ARM) | PASS |
+--------------------+----------------------+
| Ubuntu 22.04 | PASS |
+--------------------+----------------------+
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 22.04
Kernel: 5.15.0-100-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/32861/
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-21 14:14 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250321094820.3311252-2-psatheesh@marvell.com>
2025-03-21 9:15 ` |SUCCESS| pw152516-152517 [PATCH 2/2] common/cnxk: defragment MCAM bank during allocation qemudev
2025-03-21 9:20 ` qemudev
2025-03-21 9:48 ` |SUCCESS| pw152517 " checkpatch
2025-03-21 11:24 ` |SUCCESS| pw152517 [dpdk-dev] " 0-day Robot
2025-03-21 12:24 ` |SUCCESS| pw152516-152517 [PATCH] [2/2] common/cnxk: defragment MCAM dpdklab
2025-03-21 12:38 ` dpdklab
2025-03-21 12:44 ` |PENDING| " dpdklab
2025-03-21 12:48 ` |SUCCESS| " dpdklab
2025-03-21 12:50 ` dpdklab
2025-03-21 12:54 ` dpdklab
2025-03-21 13:02 ` dpdklab
2025-03-21 13:03 ` dpdklab
2025-03-21 13:06 ` dpdklab
2025-03-21 13:12 ` dpdklab
2025-03-21 13:21 ` dpdklab
2025-03-21 13:25 ` dpdklab
2025-03-21 13:25 ` dpdklab
2025-03-21 13:27 ` dpdklab
2025-03-21 13:28 ` dpdklab
2025-03-21 13:37 ` dpdklab
2025-03-21 13:40 ` dpdklab
2025-03-21 13:41 ` dpdklab
2025-03-21 13:43 ` |PENDING| " dpdklab
2025-03-21 13:44 ` |SUCCESS| " dpdklab
2025-03-21 13:46 ` |PENDING| " dpdklab
2025-03-21 14:05 ` dpdklab
2025-03-21 14:14 ` dpdklab [this message]
2025-03-21 14:14 ` |SUCCESS| " dpdklab
2025-03-21 14:54 ` |PENDING| " dpdklab
2025-03-21 14:57 ` |SUCCESS| " dpdklab
2025-03-21 15:02 ` |PENDING| " dpdklab
2025-03-21 15:06 ` |SUCCESS| " dpdklab
2025-03-21 15:19 ` dpdklab
2025-03-21 15:22 ` dpdklab
2025-03-21 15:34 ` dpdklab
2025-03-21 15:35 ` dpdklab
2025-03-21 15:35 ` dpdklab
2025-03-21 15:45 ` dpdklab
2025-03-21 15:46 ` dpdklab
2025-03-21 15:51 ` dpdklab
2025-03-21 16:02 ` dpdklab
2025-03-21 16:16 ` dpdklab
2025-03-21 16:57 ` dpdklab
2025-03-21 17:01 ` dpdklab
2025-03-21 17:08 ` dpdklab
2025-03-21 17:11 ` dpdklab
2025-03-21 17:12 ` dpdklab
2025-03-21 17:13 ` dpdklab
2025-03-21 17:30 ` dpdklab
2025-03-21 18:56 ` dpdklab
2025-03-21 21:37 ` dpdklab
2025-03-21 21:40 ` 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=67dd7438.050a0220.2e305f.4112SMTPIN_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).