From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw147581 [PATCH] net/mlx5/hws: fix allocation of STCs
Date: Tue, 29 Oct 2024 22:55:07 -0700 (PDT) [thread overview]
Message-ID: <6721ca3b.0d0a0220.96e97.013bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241029132403.232302-1-igozlan@nvidia.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/147581
_Testing PASS_
Submitter: Itamar Gozlan <igozlan@nvidia.com>
Date: Tuesday, October 29 2024 13:24:03
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:71c6d89b56ab044d7bdf2a93f242d0a149d171cf
147581 --> testing pass
Upstream job id: Template-DTS-Pipeline#192561
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/31748/
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-30 5:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241029132403.232302-1-igozlan@nvidia.com>
2024-10-29 12:53 ` qemudev
2024-10-29 12:57 ` qemudev
2024-10-29 13:25 ` checkpatch
2024-10-29 14:44 ` 0-day Robot
2024-10-30 5:55 ` dpdklab [this message]
2024-10-30 7:40 ` |PENDING| " dpdklab
2024-10-30 8:17 ` |SUCCESS| " dpdklab
2024-10-30 8:40 ` dpdklab
2024-10-30 9:20 ` dpdklab
2024-10-30 10:15 ` |PENDING| " dpdklab
2024-10-30 10:22 ` |SUCCESS| " dpdklab
2024-10-30 10:37 ` dpdklab
2024-10-30 10:53 ` 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=6721ca3b.0d0a0220.96e97.013bSMTPIN_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).