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| pw157756-157758 [PATCH] [v7,3/3] dts: update tx_offload te
Date: Thu, 16 Oct 2025 06:58:54 -0700 (PDT)	[thread overview]
Message-ID: <68f0fa1e.050a0220.11b5b5.289bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251016132421.12176-4-abailey@iol.unh.edu>

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

_Functional Testing PASS_

Submitter: Andrew Bailey <abailey@iol.unh.edu>
Date: Thursday, October 16 2025 13:24:21 
DPDK git baseline: Repo:dpdk-next-dts
  Branch: master
  CommitID:c1a9d3e5a721be9be66f0c4bfd9fa4d6e6af3b98

157756-157758 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#249795

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

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-16 13:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251016132421.12176-4-abailey@iol.unh.edu>
2025-10-16 13:28 ` |SUCCESS| pw157758 [PATCH v7 3/3] dts: update tx_offload test from legacy dts to next dts checkpatch
2025-10-16 13:48 ` |FAILURE| pw157756-157758 [PATCH] [v7,3/3] dts: update tx_offload te dpdklab
2025-10-16 13:50 ` |PENDING| " dpdklab
2025-10-16 13:54 ` |SUCCESS| " dpdklab
2025-10-16 13:54 ` |PENDING| " dpdklab
2025-10-16 13:58 ` dpdklab [this message]
2025-10-16 14:03 ` dpdklab
2025-10-16 14:13 ` |SUCCESS| " dpdklab
2025-10-16 14:14 ` dpdklab
2025-10-16 14:16 ` dpdklab
2025-10-16 14:16 ` dpdklab
2025-10-16 14:17 ` |PENDING| " dpdklab
2025-10-16 14:26 ` |SUCCESS| " dpdklab
2025-10-16 14:32 ` dpdklab
2025-10-16 14:35 ` dpdklab
2025-10-16 14:43 ` dpdklab
2025-10-16 14:46 ` dpdklab
2025-10-16 14:48 ` dpdklab
2025-10-16 15:00 ` dpdklab
2025-10-16 15:02 ` dpdklab
2025-10-16 16:45 ` dpdklab
2025-10-16 19:42 ` dpdklab
2025-10-16 19:58 ` dpdklab
2025-10-17  1:19 ` |WARNING| " dpdklab
2025-10-17  1:22 ` |PENDING| " dpdklab
2025-10-17  1:46 ` |WARNING| " dpdklab
2025-10-17  9:33 ` |SUCCESS| " dpdklab
2025-10-17 13:20 ` 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=68f0fa1e.050a0220.11b5b5.289bSMTPIN_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).