From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152247 [PATCH] net/mlx5/hws: fix incorrect DV FT type co
Date: Wed, 05 Mar 2025 09:07:54 -0800 (PST) [thread overview]
Message-ID: <67c884ea.050a0220.2433b9.c9a8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250305132353.46724-1-dsosnowski@nvidia.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/152247
_Testing PASS_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Wednesday, March 05 2025 13:23:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cf35973540c8bb4ca5c7d105985a65a3602e5475
152247 --> testing pass
Upstream job id: Template-DTS-Pipeline#216240
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/32755/
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-05 17:07 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250305132353.46724-1-dsosnowski@nvidia.com>
2025-03-05 12:57 ` |SUCCESS| pw152247 [PATCH] net/mlx5/hws: fix incorrect DV FT type convert qemudev
2025-03-05 13:01 ` qemudev
2025-03-05 13:25 ` checkpatch
2025-03-05 14:24 ` |FAILURE| " 0-day Robot
2025-03-05 16:14 ` |SUCCESS| pw152247 [PATCH] net/mlx5/hws: fix incorrect DV FT type co dpdklab
2025-03-05 16:21 ` dpdklab
2025-03-05 16:23 ` dpdklab
2025-03-05 16:23 ` dpdklab
2025-03-05 16:35 ` dpdklab
2025-03-05 16:35 ` dpdklab
2025-03-05 16:47 ` |FAILURE| " dpdklab
2025-03-05 17:02 ` |SUCCESS| " dpdklab
2025-03-05 17:07 ` dpdklab [this message]
2025-03-05 17:08 ` dpdklab
2025-03-05 17:09 ` |PENDING| " dpdklab
2025-03-05 17:16 ` |SUCCESS| " dpdklab
2025-03-05 17:18 ` dpdklab
2025-03-05 17:18 ` dpdklab
2025-03-05 17:21 ` |PENDING| " dpdklab
2025-03-05 17:28 ` |SUCCESS| " dpdklab
2025-03-05 17:28 ` |PENDING| " dpdklab
2025-03-05 17:30 ` |SUCCESS| " dpdklab
2025-03-05 17:42 ` |FAILURE| " dpdklab
2025-03-05 17:43 ` |SUCCESS| " dpdklab
2025-03-05 17:44 ` |PENDING| " dpdklab
2025-03-05 17:54 ` |SUCCESS| " dpdklab
2025-03-05 17:55 ` dpdklab
2025-03-05 18:01 ` dpdklab
2025-03-05 18:03 ` dpdklab
2025-03-05 18:18 ` |PENDING| " dpdklab
2025-03-05 18:18 ` dpdklab
2025-03-05 18:24 ` dpdklab
2025-03-05 18:30 ` |SUCCESS| " dpdklab
2025-03-05 18:43 ` |PENDING| " dpdklab
2025-03-05 18:46 ` |SUCCESS| " dpdklab
2025-03-05 18:51 ` dpdklab
2025-03-05 18:57 ` dpdklab
2025-03-05 19:00 ` dpdklab
2025-03-05 19:15 ` dpdklab
2025-03-05 19:44 ` dpdklab
2025-03-05 19:56 ` dpdklab
2025-03-05 19:59 ` dpdklab
2025-03-06 1:28 ` dpdklab
2025-03-06 3:20 ` dpdklab
2025-03-06 3:26 ` dpdklab
2025-03-06 3:29 ` dpdklab
2025-03-06 3:31 ` dpdklab
2025-03-06 3:32 ` dpdklab
2025-03-06 3:43 ` dpdklab
2025-03-06 3:47 ` dpdklab
2025-03-06 3:52 ` dpdklab
2025-03-06 3:54 ` dpdklab
2025-03-06 4:47 ` 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=67c884ea.050a0220.2433b9.c9a8SMTPIN_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).