From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152746-152747 [PATCH] [2/2] dts: update dpdk-devbind scr
Date: Fri, 04 Apr 2025 09:04:27 -0700 (PDT) [thread overview]
Message-ID: <67f0030b.170a0220.1e6a47.a9feSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250403023059.1762841-3-probb@iol.unh.edu>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152747
_Functional Testing PASS_
Submitter: Patrick Robb <probb@iol.unh.edu>
Date: Thursday, April 03 2025 02:30:59
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7246d0a80cb79a04e1334393ef507aa4ef7accd9
152746-152747 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#220119
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/32936/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2025-04-04 16:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250403023059.1762841-3-probb@iol.unh.edu>
2025-04-03 2:07 ` |SUCCESS| pw152746-152747 [PATCH 2/2] dts: update dpdk-devbind script regex qemudev
2025-04-03 2:12 ` qemudev
2025-04-03 2:36 ` |SUCCESS| pw152747 " checkpatch
2025-04-03 3:16 ` |WARNING| pw152746-152747 [PATCH] [2/2] dts: update dpdk-devbind scr dpdklab
2025-04-03 3:41 ` |SUCCESS| " dpdklab
2025-04-03 3:42 ` |SUCCESS| pw152747 [PATCH 2/2] dts: update dpdk-devbind script regex 0-day Robot
2025-04-03 3:42 ` |SUCCESS| pw152746-152747 [PATCH] [2/2] dts: update dpdk-devbind scr dpdklab
2025-04-03 3:44 ` dpdklab
2025-04-03 3:48 ` |FAILURE| " dpdklab
2025-04-03 3:57 ` dpdklab
2025-04-03 3:58 ` |PENDING| " dpdklab
2025-04-03 4:05 ` dpdklab
2025-04-03 4:07 ` dpdklab
2025-04-03 4:24 ` |SUCCESS| " dpdklab
2025-04-03 4:54 ` dpdklab
2025-04-03 5:09 ` dpdklab
2025-04-03 5:18 ` dpdklab
2025-04-03 5:19 ` dpdklab
2025-04-03 5:24 ` dpdklab
2025-04-03 5:33 ` dpdklab
2025-04-03 5:34 ` dpdklab
2025-04-03 8:56 ` dpdklab
2025-04-03 19:24 ` |FAILURE| " dpdklab
2025-04-03 21:43 ` |SUCCESS| " dpdklab
2025-04-03 22:07 ` |FAILURE| " dpdklab
2025-04-04 16:04 ` dpdklab [this message]
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=67f0030b.170a0220.1e6a47.a9feSMTPIN_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).