automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw147582 [PATCH] net/mlx5: fix PMD compilation in non-HWS
Date: Tue, 29 Oct 2024 22:26:13 -0700 (PDT)	[thread overview]
Message-ID: <6721c375.170a0220.46016.f057SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241029133415.583413-1-getelson@nvidia.com>

Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/147582

_Testing PASS_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Tuesday, October 29 2024 13:34:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:71c6d89b56ab044d7bdf2a93f242d0a149d171cf

147582 --> testing pass

Upstream job id: Template-DTS-Pipeline#192531

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/31749/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-10-30  5:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241029133415.583413-1-getelson@nvidia.com>
2024-10-29 13:17 ` |SUCCESS| pw147582 [PATCH] net/mlx5: fix PMD compilation in non-HWS setup qemudev
2024-10-29 13:21 ` qemudev
2024-10-29 13:35 ` checkpatch
2024-10-30  5:26 ` dpdklab [this message]
2024-10-30  7:23 ` |PENDING| pw147582 [PATCH] net/mlx5: fix PMD compilation in non-HWS dpdklab
2024-10-30  7:24 ` dpdklab
2024-10-30  7:43 ` |SUCCESS| " dpdklab
2024-10-30  7:52 ` dpdklab
2024-10-30  8:16 ` 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=6721c375.170a0220.46016.f057SMTPIN_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).