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| pw151584 [PATCH] ethdev: fix get_reg_info
Date: Tue, 18 Feb 2025 10:54:39 -0800 (PST)	[thread overview]
Message-ID: <67b4d76f.c80a0220.2cc31a.d934SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250218115828.2107335-1-thierry.herbelot@6wind.com>

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

_Testing PASS_

Submitter: Thierry Herbelot <thierry.herbelot@6wind.com>
Date: Tuesday, February 18 2025 11:58:28 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:968f7b6d7b6a7e60e6e551db430c4eecaccbbfd2

151584 --> testing pass

Upstream job id: Template-DTS-Pipeline#213126

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-02-18 18:54 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250218115828.2107335-1-thierry.herbelot@6wind.com>
2025-02-18 11:25 ` qemudev
2025-02-18 11:29 ` qemudev
2025-02-18 12:00 ` checkpatch
2025-02-18 14:24 ` 0-day Robot
2025-02-18 17:36 ` dpdklab
2025-02-18 17:41 ` dpdklab
2025-02-18 17:46 ` dpdklab
2025-02-18 18:19 ` dpdklab
2025-02-18 18:34 ` |PENDING| " dpdklab
2025-02-18 18:46 ` |SUCCESS| " dpdklab
2025-02-18 18:54 ` dpdklab [this message]
2025-02-18 18:56 ` dpdklab
2025-02-18 19:06 ` dpdklab
2025-02-18 19:07 ` dpdklab
2025-02-18 19:09 ` |PENDING| " dpdklab
2025-02-18 19:09 ` dpdklab
2025-02-18 19:25 ` dpdklab
2025-02-18 19:35 ` |SUCCESS| " dpdklab
2025-02-18 19:43 ` dpdklab
2025-02-18 19:47 ` |PENDING| " dpdklab
2025-02-18 19:48 ` |SUCCESS| " dpdklab
2025-02-18 20:03 ` dpdklab
2025-02-18 20:03 ` dpdklab
2025-02-18 20:04 ` dpdklab
2025-02-18 20:06 ` |PENDING| " dpdklab
2025-02-18 20:12 ` |SUCCESS| " dpdklab
2025-02-18 20:37 ` dpdklab
2025-02-18 20:37 ` |PENDING| " dpdklab
2025-02-18 20:40 ` |SUCCESS| " dpdklab
2025-02-18 20:47 ` dpdklab
2025-02-18 20:51 ` dpdklab
2025-02-18 20:55 ` dpdklab
2025-02-18 21:21 ` |PENDING| " dpdklab
2025-02-18 21:33 ` |SUCCESS| " dpdklab
2025-02-18 21:33 ` dpdklab
2025-02-18 21:38 ` dpdklab
2025-02-18 21:54 ` dpdklab
2025-02-18 22:55 ` dpdklab
2025-02-18 22:57 ` dpdklab
2025-02-19 10:32 ` dpdklab
2025-02-19 10:59 ` 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=67b4d76f.c80a0220.2cc31a.d934SMTPIN_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).