From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw147735-147736 [PATCH] [3/3] net/mlx5: fix stub for HWS c
Date: Wed, 30 Oct 2024 17:31:33 -0700 (PDT) [thread overview]
Message-ID: <6722cfe5.050a0220.40572.17d2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241030105412.482107-4-dsosnowski@nvidia.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/147736
_Testing PASS_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Wednesday, October 30 2024 10:54:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:69461d18dfd5efab8a126b9ec209966d5013df0c
147735-147736 --> testing pass
Upstream job id: Template-DTS-Pipeline#193026
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/31772/
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:[~2024-10-31 0:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241030105412.482107-4-dsosnowski@nvidia.com>
2024-10-30 10:25 ` |SUCCESS| pw147735-147736 [PATCH 3/3] net/mlx5: fix stub for HWS context validation qemudev
2024-10-30 10:29 ` qemudev
2024-10-30 10:55 ` |SUCCESS| pw147736 " checkpatch
2024-10-31 0:31 ` dpdklab [this message]
2024-10-31 2:31 ` |SUCCESS| pw147735-147736 [PATCH] [3/3] net/mlx5: fix stub for HWS c dpdklab
2024-10-31 3:27 ` dpdklab
2024-10-31 4:18 ` dpdklab
2024-10-31 5:16 ` |PENDING| " 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=6722cfe5.050a0220.40572.17d2SMTPIN_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).