From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw156640-156643 [PATCH] [v2,4/4] usertool: add a script to
Date: Tue, 16 Sep 2025 08:51:15 -0700 (PDT) [thread overview]
Message-ID: <68c98773.630a0220.11a856.3437SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250916151207.556618-5-shperetz@nvidia.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/156643
_Functional Testing PASS_
Submitter: Shani Peretz <shperetz@nvidia.com>
Date: Tuesday, September 16 2025 15:12:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:426977791364cc29046ce22e9d8ca77eb0dee453
156640-156643 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#244847
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/34079/
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-09-16 15:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250916151207.556618-5-shperetz@nvidia.com>
2025-09-16 14:39 ` |SUCCESS| pw156640-156643 [PATCH v2 4/4] usertool: add a script to parse mbuf history dump qemudev
2025-09-16 14:44 ` qemudev
2025-09-16 15:10 ` |SUCCESS| pw156643 " checkpatch
2025-09-16 15:47 ` |SUCCESS| pw156640-156643 [PATCH] [v2,4/4] usertool: add a script to dpdklab
2025-09-16 15:49 ` |PENDING| " dpdklab
2025-09-16 15:51 ` dpdklab [this message]
2025-09-16 15:59 ` dpdklab
2025-09-16 16:14 ` |SUCCESS| " dpdklab
2025-09-16 16:15 ` |PENDING| " dpdklab
2025-09-16 16:21 ` |SUCCESS| " dpdklab
2025-09-16 16:22 ` dpdklab
2025-09-16 16:27 ` |PENDING| " dpdklab
2025-09-16 16:36 ` |FAILURE| pw156643 [PATCH v2 4/4] usertool: add a script to parse mbuf history dump 0-day Robot
2025-09-16 17:00 ` |WARNING| pw156640-156643 [PATCH] [v2,4/4] usertool: add a script to dpdklab
2025-09-16 17:09 ` dpdklab
2025-09-16 17:13 ` |SUCCESS| " dpdklab
2025-09-16 17:15 ` dpdklab
2025-09-16 17:30 ` dpdklab
2025-09-16 17:46 ` dpdklab
2025-09-16 22:14 ` dpdklab
2025-09-16 22:17 ` dpdklab
2025-09-16 22:39 ` dpdklab
2025-09-17 1:35 ` dpdklab
2025-09-17 1:42 ` 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=68c98773.630a0220.11a856.3437SMTPIN_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).