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,
	Bruce Richardson <bruce.richardson@intel.com>
Subject: |SUCCESS| pw159303 [PATCH] net/intel: cache mbuf fast release mempoo
Date: Fri, 12 Dec 2025 09:32:35 -0800 (PST)	[thread overview]
Message-ID: <693c51b3.170a0220.12f2a.6a4eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251212111136.103137-1-mb@smartsharesystems.com>

Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/159303

_Functional Testing PASS_

Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Friday, December 12 2025 11:11:36 
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: master
  CommitID:00597edd3c11ecea67d3296300b0079ee4b4b2b4

159303 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#258304

Test environment and result as below:

Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc

Aggregate Results by Test Suite
+----------------+--------+
|   Test Suite   | Result |
+================+========+
| cmdline        |  PASS  |
+----------------+--------+
| rxtx_callbacks |  PASS  |
+----------------+--------+


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34755/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-12-12 17:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251212111136.103137-1-mb@smartsharesystems.com>
2025-12-12 11:01 ` |SUCCESS| pw159303 [PATCH] net/intel: cache mbuf fast release mempool qemudev
2025-12-12 11:07 ` qemudev
2025-12-12 11:12 ` |WARNING| " checkpatch
2025-12-12 12:51 ` |SUCCESS| " 0-day Robot
2025-12-12 15:06 ` |SUCCESS| pw159303 [PATCH] net/intel: cache mbuf fast release mempoo dpdklab
2025-12-12 15:06 ` |PENDING| " dpdklab
2025-12-12 15:08 ` dpdklab
2025-12-12 15:08 ` dpdklab
2025-12-12 15:09 ` dpdklab
2025-12-12 15:14 ` dpdklab
2025-12-12 15:17 ` |SUCCESS| " dpdklab
2025-12-12 15:20 ` dpdklab
2025-12-12 15:49 ` dpdklab
2025-12-12 15:57 ` dpdklab
2025-12-12 16:14 ` dpdklab
2025-12-12 17:32 ` dpdklab [this message]
2025-12-12 17:58 ` |PENDING| " dpdklab
2025-12-12 18:04 ` |SUCCESS| " dpdklab
2025-12-12 18:16 ` dpdklab
2025-12-12 18:32 ` 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=693c51b3.170a0220.12f2a.6a4eSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bruce.richardson@intel.com \
    --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).