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| pw155849-155851 [PATCH] [3/3] bbdev: wrong fix for MinGW 1
Date: Wed, 13 Aug 2025 23:38:34 -0700 (PDT)	[thread overview]
Message-ID: <689d846a.170a0220.3441e7.26fcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250813152829.457463-4-thomas@monjalon.net>

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

_Functional Testing PASS_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Wednesday, August 13 2025 15:25:25 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:38543d33bd47fc0ee21f59db80a8763620741879

155849-155851 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#240309

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-08-14  6:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250813152829.457463-4-thomas@monjalon.net>
2025-08-13 14:55 ` |SUCCESS| pw155849-155851 [PATCH 3/3] bbdev: wrong fix for MinGW 13 qemudev
2025-08-13 15:00 ` qemudev
2025-08-13 15:27 ` |SUCCESS| pw155851 " checkpatch
2025-08-13 16:35 ` 0-day Robot
2025-08-14  6:10 ` |SUCCESS| pw155849-155851 [PATCH] [3/3] bbdev: wrong fix for MinGW 1 dpdklab
2025-08-14  6:38 ` dpdklab [this message]
2025-08-14  6:45 ` |FAILURE| " dpdklab
2025-08-14  6:49 ` |SUCCESS| " dpdklab
2025-08-14  6:54 ` |PENDING| " dpdklab
2025-08-14  6:57 ` |SUCCESS| " dpdklab
2025-08-14  6:57 ` |FAILURE| " dpdklab
2025-08-14  7:02 ` |SUCCESS| " dpdklab
2025-08-14  7:07 ` |PENDING| " dpdklab
2025-08-14  7:13 ` |FAILURE| " dpdklab
2025-08-14  7:14 ` dpdklab
2025-08-14  7:23 ` dpdklab
2025-08-14  7:38 ` dpdklab
2025-08-14  8:26 ` |SUCCESS| " dpdklab
2025-08-14  8:39 ` dpdklab
2025-08-14  8:50 ` |FAILURE| " dpdklab
2025-08-15 15:36 ` |SUCCESS| " 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=689d846a.170a0220.3441e7.26fcSMTPIN_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).