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| pw152867 [PATCH] app/testpmd: fix dump command list for MS
Date: Thu, 10 Apr 2025 13:50:07 -0700 (PDT)	[thread overview]
Message-ID: <67f82eff.170a0220.3c5a87.d868SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250410160237.3067629-1-david.marchand@redhat.com>

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

_Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Thursday, April 10 2025 16:02:36 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b69fb7abb6d211cb74284029c6cdb2066b9ac0e9

152867 --> testing pass

Upstream job id: Template-DTS-Pipeline#221200

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-04-10 20:50 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250410160237.3067629-1-david.marchand@redhat.com>
2025-04-10 15:29 ` |SUCCESS| pw152867 [PATCH] app/testpmd: fix dump command list for MSVC qemudev
2025-04-10 15:33 ` qemudev
2025-04-10 16:04 ` checkpatch
2025-04-10 17:46 ` 0-day Robot
2025-04-10 20:04 ` |SUCCESS| pw152867 [PATCH] app/testpmd: fix dump command list for MS dpdklab
2025-04-10 20:12 ` dpdklab
2025-04-10 20:15 ` dpdklab
2025-04-10 20:24 ` |PENDING| " dpdklab
2025-04-10 20:25 ` |SUCCESS| " dpdklab
2025-04-10 20:30 ` dpdklab
2025-04-10 20:31 ` dpdklab
2025-04-10 20:35 ` dpdklab
2025-04-10 20:50 ` dpdklab [this message]
2025-04-10 20:52 ` |PENDING| " dpdklab
2025-04-10 20:55 ` |SUCCESS| " dpdklab
2025-04-10 21:01 ` |PENDING| " dpdklab
2025-04-10 21:10 ` |SUCCESS| " dpdklab
2025-04-10 21:11 ` dpdklab
2025-04-10 21:15 ` |PENDING| " dpdklab
2025-04-10 21:20 ` |SUCCESS| " dpdklab
2025-04-10 21:20 ` |PENDING| " dpdklab
2025-04-10 21:22 ` |SUCCESS| " dpdklab
2025-04-10 21:25 ` |PENDING| " dpdklab
2025-04-10 21:28 ` dpdklab
2025-04-10 21:38 ` |SUCCESS| " dpdklab
2025-04-10 21:44 ` dpdklab
2025-04-10 21:45 ` dpdklab
2025-04-10 21:46 ` dpdklab
2025-04-10 21:47 ` |PENDING| " dpdklab
2025-04-10 21:56 ` |SUCCESS| " dpdklab
2025-04-10 22:04 ` dpdklab
2025-04-10 22:16 ` dpdklab
2025-04-10 22:16 ` |PENDING| " dpdklab
2025-04-10 22:28 ` |SUCCESS| " dpdklab
2025-04-10 22:33 ` dpdklab
2025-04-10 22:59 ` |PENDING| " dpdklab
2025-04-10 23:17 ` |SUCCESS| " dpdklab
2025-04-10 23:39 ` dpdklab
2025-04-10 23:41 ` dpdklab
2025-04-10 23:52 ` dpdklab
2025-04-10 23:54 ` dpdklab
2025-04-11  0:02 ` dpdklab
2025-04-11  0:17 ` dpdklab
2025-04-11  0:45 ` dpdklab
2025-04-11  2:00 ` dpdklab
2025-04-11  2:06 ` dpdklab
2025-04-11 22:04 ` dpdklab
2025-04-11 22:09 ` 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=67f82eff.170a0220.3c5a87.d868SMTPIN_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).