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, Akhil Goyal <gakhil@marvell.com>
Subject: |SUCCESS| pw157330 [PATCH] [v2] compressdev: update device ID valida
Date: Wed, 08 Oct 2025 03:34:05 -0700 (PDT)	[thread overview]
Message-ID: <68e63e1d.050a0220.330fcf.70deSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251008095950.3078552-1-ashishg@marvell.com>

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

_Functional Testing PASS_

Submitter: Ashish Gupta <ashishg@marvell.com>
Date: Wednesday, October 08 2025 09:59:41 
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: master
  CommitID:2aa7141a4e2c78e3cce03dbd613532a2166123c1

157330 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#248500

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-10-08 10:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251008095950.3078552-1-ashishg@marvell.com>
2025-10-08  9:31 ` |SUCCESS| pw157330 [PATCH v2] compressdev: update device ID validation check qemudev
2025-10-08  9:36 ` qemudev
2025-10-08 10:00 ` checkpatch
2025-10-08 10:29 ` |SUCCESS| pw157330 [PATCH] [v2] compressdev: update device ID valida dpdklab
2025-10-08 10:33 ` dpdklab
2025-10-08 10:34 ` dpdklab [this message]
2025-10-08 10:40 ` dpdklab
2025-10-08 10:43 ` dpdklab
2025-10-08 10:58 ` dpdklab
2025-10-08 11:01 ` dpdklab
2025-10-08 11:28 ` |SUCCESS| pw157330 [PATCH v2] compressdev: update device ID validation check 0-day Robot
2025-10-08 11:28 ` 0-day Robot
2025-10-08 11:34 ` |SUCCESS| pw157330 [PATCH] [v2] compressdev: update device ID valida dpdklab
2025-10-08 11:38 ` |PENDING| " dpdklab
2025-10-08 11:48 ` |SUCCESS| " dpdklab
2025-10-08 11:50 ` dpdklab
2025-10-08 12:02 ` |PENDING| " dpdklab
2025-10-08 12:14 ` |SUCCESS| " dpdklab
2025-10-08 12:36 ` dpdklab
2025-10-08 12:48 ` dpdklab
2025-10-08 12:59 ` dpdklab
2025-10-08 13:08 ` dpdklab
2025-10-08 13:24 ` 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=68e63e1d.050a0220.330fcf.70deSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=gakhil@marvell.com \
    --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).