From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152045-152050 [PATCH] [v2,6/6] dts: add NIC capabilities
Date: Tue, 25 Feb 2025 17:03:09 -0800 (PST) [thread overview]
Message-ID: <67be684d.050a0220.1b8ab2.9100SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250225153345.331216-7-thomas.wilks@arm.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152050
_Functional Testing PASS_
Submitter: Thomas Wilks <thomas.wilks@arm.com>
Date: Tuesday, February 25 2025 15:33:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c807af409e52bbd6899ea5cc49693f800a125a26
152045-152050 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#214468
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/32682/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-02-26 1:03 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250225153345.331216-7-thomas.wilks@arm.com>
2025-02-25 15:11 ` |SUCCESS| pw152045-152050 [PATCH v2 6/6] dts: add NIC capabilities for hash algorithms qemudev
2025-02-25 15:16 ` qemudev
2025-02-25 15:34 ` |SUCCESS| pw152050 " checkpatch
2025-02-25 16:24 ` 0-day Robot
2025-02-25 21:37 ` |SUCCESS| pw152045-152050 [PATCH] [v2,6/6] dts: add NIC capabilities dpdklab
2025-02-25 21:43 ` dpdklab
2025-02-25 21:49 ` dpdklab
2025-02-25 21:56 ` dpdklab
2025-02-25 22:06 ` dpdklab
2025-02-25 22:13 ` dpdklab
2025-02-25 23:32 ` |PENDING| " dpdklab
2025-02-25 23:39 ` |SUCCESS| " dpdklab
2025-02-25 23:40 ` dpdklab
2025-02-25 23:57 ` dpdklab
2025-02-25 23:58 ` dpdklab
2025-02-26 0:08 ` dpdklab
2025-02-26 0:13 ` dpdklab
2025-02-26 0:56 ` |PENDING| " dpdklab
2025-02-26 0:57 ` dpdklab
2025-02-26 1:03 ` dpdklab [this message]
2025-02-26 1:17 ` |SUCCESS| " dpdklab
2025-02-26 1:26 ` dpdklab
2025-02-26 1:44 ` dpdklab
2025-02-26 1:46 ` dpdklab
2025-02-26 1:48 ` dpdklab
2025-02-26 1:56 ` dpdklab
2025-02-26 1:57 ` dpdklab
2025-02-26 2:04 ` dpdklab
2025-02-26 2:14 ` dpdklab
2025-02-26 2:15 ` dpdklab
2025-02-26 2:58 ` |PENDING| " dpdklab
2025-02-26 3:11 ` dpdklab
2025-02-26 3:29 ` |SUCCESS| " dpdklab
2025-02-26 3:50 ` dpdklab
2025-02-26 3:57 ` dpdklab
2025-02-26 4:00 ` dpdklab
2025-02-26 4:02 ` dpdklab
2025-02-26 5:50 ` |PENDING| " dpdklab
2025-02-26 6:40 ` |SUCCESS| " dpdklab
2025-02-26 7:23 ` dpdklab
2025-02-26 7: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=67be684d.050a0220.1b8ab2.9100SMTPIN_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).