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| pw151772 [PATCH] [v3] net/mana: use mana_local_data for tr
Date: Thu, 20 Feb 2025 19:44:07 -0800 (PST)	[thread overview]
Message-ID: <67b7f687.170a0220.230b8e.172aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1740094322-10919-1-git-send-email-longli@linuxonhyperv.com>

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

_Testing PASS_

Submitter: Long Li <longli@linuxonhyperv.com>
Date: Thursday, February 20 2025 23:32:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3497d187f963e5fddca607637f6a42b8b944fa49

151772 --> testing pass

Upstream job id: Template-DTS-Pipeline#213595

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

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-21  3:44 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1740094322-10919-1-git-send-email-longli@linuxonhyperv.com>
2025-02-20 23:03 ` |SUCCESS| pw151772 [Patch v3] net/mana: use mana_local_data for tracking usage data for primary process qemudev
2025-02-20 23:07 ` qemudev
2025-02-20 23:33 ` |WARNING| " checkpatch
2025-02-21  0:44 ` |SUCCESS| " 0-day Robot
2025-02-21  2:36 ` |SUCCESS| pw151772 [PATCH] [v3] net/mana: use mana_local_data for tr dpdklab
2025-02-21  2:37 ` dpdklab
2025-02-21  2:38 ` dpdklab
2025-02-21  2:41 ` dpdklab
2025-02-21  3:15 ` dpdklab
2025-02-21  3:21 ` dpdklab
2025-02-21  3:30 ` |PENDING| " dpdklab
2025-02-21  3:33 ` |SUCCESS| " dpdklab
2025-02-21  3:42 ` dpdklab
2025-02-21  3:44 ` dpdklab [this message]
2025-02-21  3:44 ` dpdklab
2025-02-21  3:56 ` |PENDING| " dpdklab
2025-02-21  4:10 ` dpdklab
2025-02-21  4:11 ` dpdklab
2025-02-21  4:28 ` |SUCCESS| " dpdklab
2025-02-21  4:46 ` |PENDING| " dpdklab
2025-02-21  4:48 ` dpdklab
2025-02-21  4:56 ` |SUCCESS| " dpdklab
2025-02-21  4:56 ` dpdklab
2025-02-21  5:10 ` dpdklab
2025-02-21  5:10 ` dpdklab
2025-02-21  5:11 ` dpdklab
2025-02-21  5:13 ` dpdklab
2025-02-21  5:27 ` dpdklab
2025-02-21  5:27 ` |PENDING| " dpdklab
2025-02-21  5:31 ` dpdklab
2025-02-21  5:39 ` |SUCCESS| " dpdklab
2025-02-21  6:07 ` dpdklab
2025-02-21  6:07 ` dpdklab
2025-02-21  6:23 ` dpdklab
2025-02-21  6:25 ` dpdklab
2025-02-21  6:55 ` dpdklab
2025-02-21  6:55 ` dpdklab
2025-02-21  6:56 ` dpdklab
2025-02-21  6:56 ` dpdklab
2025-02-21  7:32 ` dpdklab
2025-02-21 17:40 ` 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=67b7f687.170a0220.230b8e.172aSMTPIN_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).