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: |PENDING| pw156532 [PATCH] net/intel: remove unused Tx struct member
Date: Thu, 18 Sep 2025 11:26:09 -0700 (PDT)	[thread overview]
Message-ID: <68cc4ec1.050a0220.13a99.15e4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250910080616.892711-1-bruce.richardson@intel.com>

Test-Label: iol-sample-apps-testing
Test-Status: PENDING
http://dpdk.org/patch/156532

_Testing pending RETEST #1_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Wednesday, September 10 2025 08:06:16 
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: master
  CommitID:4159ea62922ce41566c7bab44655ad78bee85458

156532 --> testing pending

Upstream job id: Template-DTS-Pipeline#245241

Test environment and result as below:

+--------------+----------------------+----------------------+
| Environment  | dpdk_fips_validation | compressdev_zlib_pmd |
+==============+======================+======================+
| Ubuntu 20.04 | PEND                 | SKIPPED              |
+--------------+----------------------+----------------------+
| Ubuntu 22.04 | SKIPPED              | PASS                 |
+--------------+----------------------+----------------------+


Ubuntu 20.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 22.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-09-18 18:26 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250910080616.892711-1-bruce.richardson@intel.com>
2025-09-10  7:31 ` |SUCCESS| " qemudev
2025-09-10  7:36 ` qemudev
2025-09-10  8:04 ` checkpatch
2025-09-10  9:08 ` |PENDING| " dpdklab
2025-09-10  9:11 ` |SUCCESS| " dpdklab
2025-09-10  9:12 ` dpdklab
2025-09-10  9:29 ` 0-day Robot
2025-09-10  9:29 ` 0-day Robot
2025-09-10  9:47 ` dpdklab
2025-09-10  9:56 ` dpdklab
2025-09-10 11:28 ` dpdklab
2025-09-10 11:46 ` dpdklab
2025-09-10 12:22 ` dpdklab
2025-09-10 13:02 ` |PENDING| " dpdklab
2025-09-10 13:04 ` dpdklab
2025-09-10 13:05 ` |FAILURE| " dpdklab
2025-09-10 13:27 ` |SUCCESS| " dpdklab
2025-09-10 13:27 ` dpdklab
2025-09-10 13:31 ` |WARNING| " dpdklab
2025-09-10 13:59 ` dpdklab
2025-09-10 14:14 ` |SUCCESS| " dpdklab
2025-09-10 14:51 ` dpdklab
2025-09-10 16:00 ` |PENDING| " dpdklab
2025-09-10 16:06 ` |SUCCESS| " dpdklab
2025-09-10 16:27 ` |WARNING| " dpdklab
2025-09-10 16:32 ` |SUCCESS| " dpdklab
2025-09-10 16:56 ` |FAILURE| " dpdklab
2025-09-10 17:25 ` |SUCCESS| " dpdklab
2025-09-10 17:28 ` |FAILURE| " dpdklab
2025-09-10 17:50 ` |SUCCESS| " dpdklab
2025-09-10 18:00 ` |FAILURE| " dpdklab
2025-09-10 18:18 ` dpdklab
2025-09-10 23:02 ` dpdklab
2025-09-11  4:09 ` dpdklab
2025-09-11  5:20 ` |WARNING| " dpdklab
2025-09-11  8:10 ` qemudev
2025-09-11  9:06 ` qemudev
2025-09-12 20:36 ` |SUCCESS| " dpdklab
2025-09-18 18:14 ` |PENDING| " dpdklab
2025-09-18 18:16 ` dpdklab
2025-09-18 18:17 ` |SUCCESS| " dpdklab
2025-09-18 18:22 ` dpdklab
2025-09-18 18:26 ` dpdklab [this message]
2025-09-18 18:29 ` |PENDING| " dpdklab
2025-09-18 18:35 ` |SUCCESS| " dpdklab
2025-09-18 18:39 ` dpdklab
2025-09-18 18:39 ` dpdklab
2025-09-18 18:47 ` dpdklab
2025-09-18 18:54 ` dpdklab
2025-09-18 18:56 ` dpdklab
2025-09-18 19:00 ` dpdklab
2025-09-18 19:01 ` dpdklab
2025-09-18 19:01 ` dpdklab
2025-09-18 19:06 ` dpdklab
2025-09-18 21:39 ` 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=68cc4ec1.050a0220.13a99.15e4SMTPIN_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).