From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152750-152753 [PATCH] [RFC,4/4] net/cnxk: report link ty
Date: Fri, 04 Apr 2025 09:43:17 -0700 (PDT) [thread overview]
Message-ID: <67f00c25.170a0220.64f18.ad12SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250403070837.926292-4-ndabilpuram@marvell.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152753
_Functional Testing PASS_
Submitter: Nithin Dabilpuram <ndabilpuram@marvell.com>
Date: Thursday, April 03 2025 07:08:37
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b40c403777e93242a377c07ff51964480d40b51d
152750-152753 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#220189
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/32939/
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:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250403070837.926292-4-ndabilpuram@marvell.com>
2025-04-03 6:35 ` |SUCCESS| pw152750-152753 [RFC PATCH 4/4] net/cnxk: report link type along with link status qemudev
2025-04-03 6:41 ` |FAILURE| " qemudev
2025-04-03 7:09 ` |SUCCESS| pw152753 " checkpatch
2025-04-03 8:02 ` |FAILURE| " 0-day Robot
2025-04-03 8:33 ` |SUCCESS| pw152750-152753 [PATCH] [RFC,4/4] net/cnxk: report link ty dpdklab
2025-04-03 8:39 ` dpdklab
2025-04-03 8:41 ` dpdklab
2025-04-03 8:55 ` dpdklab
2025-04-03 9:01 ` dpdklab
2025-04-03 9:03 ` dpdklab
2025-04-03 9:26 ` dpdklab
2025-04-03 9:37 ` |PENDING| " dpdklab
2025-04-03 9:48 ` |FAILURE| " dpdklab
2025-04-03 9:52 ` dpdklab
2025-04-03 9:53 ` dpdklab
2025-04-03 9:53 ` dpdklab
2025-04-03 9:58 ` dpdklab
2025-04-03 10:18 ` |PENDING| " dpdklab
2025-04-03 10:41 ` |FAILURE| " dpdklab
2025-04-03 10:50 ` |WARNING| " dpdklab
2025-04-03 11:41 ` |FAILURE| " dpdklab
2025-04-03 11:53 ` |SUCCESS| " dpdklab
2025-04-03 12:12 ` |FAILURE| " dpdklab
2025-04-03 12:59 ` dpdklab
2025-04-03 13:29 ` |SUCCESS| " dpdklab
2025-04-03 15:53 ` dpdklab
2025-04-03 19:32 ` dpdklab
2025-04-04 0:15 ` dpdklab
2025-04-04 0:41 ` dpdklab
2025-04-04 16:43 ` 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=67f00c25.170a0220.64f18.ad12SMTPIN_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).