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| pw153427 [PATCH] [v2] build: automatically report minimum
Date: Tue, 13 May 2025 02:36:50 -0700 (PDT)	[thread overview]
Message-ID: <682312b2.170a0220.275d92.850aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250513085956.1670288-1-bruce.richardson@intel.com>

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

_Functional Testing PASS_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tuesday, May 13 2025 08:59:42 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2bf836de46d36a81f9321f947fbfce52b3180782

153427 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#225555

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-05-13  9:36 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250513085956.1670288-1-bruce.richardson@intel.com>
2025-05-13  8:32 ` |SUCCESS| pw153427 [PATCH v2] build: automatically report minimum meson version qemudev
2025-05-13  8:36 ` qemudev
2025-05-13  9:01 ` checkpatch
2025-05-13  9:36 ` dpdklab [this message]
2025-05-13  9:38 ` |SUCCESS| pw153427 [PATCH] [v2] build: automatically report minimum dpdklab
2025-05-13  9:39 ` |FAILURE| " dpdklab
2025-05-13  9:41 ` dpdklab
2025-05-13  9:43 ` |PENDING| " dpdklab
2025-05-13  9:47 ` |SUCCESS| " dpdklab
2025-05-13  9:50 ` dpdklab
2025-05-13  9:51 ` dpdklab
2025-05-13  9:53 ` dpdklab
2025-05-13  9:55 ` dpdklab
2025-05-13  9:57 ` |FAILURE| " dpdklab
2025-05-13 10:01 ` dpdklab
2025-05-13 10:03 ` |SUCCESS| " dpdklab
2025-05-13 10:03 ` |SUCCESS| pw153427 [PATCH v2] build: automatically report minimum meson version 0-day Robot
2025-05-13 10:04 ` |FAILURE| pw153427 [PATCH] [v2] build: automatically report minimum dpdklab
2025-05-13 10:05 ` dpdklab
2025-05-13 10:05 ` dpdklab
2025-05-13 10:05 ` |SUCCESS| " dpdklab
2025-05-13 10:09 ` |FAILURE| " dpdklab
2025-05-13 10:11 ` dpdklab
2025-05-13 10:19 ` |SUCCESS| " dpdklab
2025-05-13 10:19 ` dpdklab
2025-05-13 10:20 ` dpdklab
2025-05-13 10:20 ` dpdklab
2025-05-13 10:21 ` dpdklab
2025-05-13 10:27 ` |FAILURE| " dpdklab
2025-05-13 10:32 ` dpdklab
2025-05-13 10:44 ` |SUCCESS| " dpdklab
2025-05-13 10:52 ` dpdklab
2025-05-13 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=682312b2.170a0220.275d92.850aSMTPIN_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).