From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Stephen Hemminger <stephen@networkplumber.org>
Subject: |SUCCESS| pw158307-158309 [PATCH] [v4,4/4] net/tap: configure link c
Date: Thu, 30 Oct 2025 11:30:01 -0700 (PDT) [thread overview]
Message-ID: <6903aea9.170a0220.1dd4ce.e9a1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251030175537.219641-11-rjarry@redhat.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/158309
_Functional Testing PASS_
Submitter: Robin Jarry <rjarry@redhat.com>
Date: Thursday, October 30 2025 17:55:43
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:bd9b8a264598adb8e50c1e9e5fe97e75b6009db9
158307-158309 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#252160
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/34425/
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-10-30 18:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251030175537.219641-11-rjarry@redhat.com>
2025-10-30 17:26 ` |SUCCESS| pw158307-158309 [PATCH dpdk v4 4/4] net/tap: configure link carrier qemudev
2025-10-30 17:31 ` qemudev
2025-10-30 17:57 ` |SUCCESS| pw158309 " checkpatch
2025-10-30 18:21 ` |PENDING| pw158307-158309 [PATCH] [v4,4/4] net/tap: configure link c dpdklab
2025-10-30 18:25 ` |SUCCESS| " dpdklab
2025-10-30 18:27 ` |PENDING| " dpdklab
2025-10-30 18:30 ` dpdklab [this message]
2025-10-30 18:31 ` dpdklab
2025-10-30 18:34 ` dpdklab
2025-10-30 18:34 ` |FAILURE| " dpdklab
2025-10-30 18:35 ` dpdklab
2025-10-30 18:41 ` |SUCCESS| " dpdklab
2025-10-30 18:44 ` dpdklab
2025-10-30 18:47 ` dpdklab
2025-10-30 18:55 ` |WARNING| " dpdklab
2025-10-30 19:05 ` dpdklab
2025-10-30 19:07 ` |SUCCESS| pw158309 [PATCH dpdk v4 4/4] net/tap: configure link carrier 0-day Robot
2025-10-30 19:07 ` 0-day Robot
2025-10-30 19:14 ` |SUCCESS| pw158307-158309 [PATCH] [v4,4/4] net/tap: configure link c dpdklab
2025-10-30 19:16 ` dpdklab
2025-10-30 19:24 ` dpdklab
2025-10-30 19:29 ` dpdklab
2025-10-30 19:32 ` |WARNING| " dpdklab
2025-10-30 22:58 ` |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=6903aea9.170a0220.1dd4ce.e9a1SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=stephen@networkplumber.org \
--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).