From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw157716-157715 [PATCH] [v1,2/2] benchmark report for rte_
Date: Thu, 16 Oct 2025 02:59:06 -0700 (PDT) [thread overview]
Message-ID: <68f0c1ea.170a0220.6ff2f.e8d7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251016090934.1166954-3-chen.qiguo@zte.com.cn>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/157715
_Functional Testing PASS_
Submitter: Qiguo Chen <chen.qiguo@zte.com.cn>
Date: Thursday, October 16 2025 09:09:34
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:16f4c522003dcfecf23c8d38e009b95a3bbefd03
157716-157715 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#249739
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/34296/
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-16 9:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251016090934.1166954-3-chen.qiguo@zte.com.cn>
2025-10-16 8:51 ` |SUCCESS| pw157716-157715 [PATCH v1 2/2] benchmark report for rte_memcpy qemudev
2025-10-16 8:56 ` qemudev
2025-10-16 9:25 ` |WARNING| pw157715 " checkpatch
2025-10-16 9:53 ` |PENDING| pw157716-157715 [PATCH] [v1,2/2] benchmark report for rte_ dpdklab
2025-10-16 9:55 ` |SUCCESS| " dpdklab
2025-10-16 9:55 ` |PENDING| " dpdklab
2025-10-16 9:56 ` |SUCCESS| " dpdklab
2025-10-16 9:59 ` dpdklab [this message]
2025-10-16 10:03 ` |PENDING| " dpdklab
2025-10-16 10:11 ` dpdklab
2025-10-16 10:14 ` |SUCCESS| " dpdklab
2025-10-16 10:15 ` dpdklab
2025-10-16 10:16 ` dpdklab
2025-10-16 10:26 ` dpdklab
2025-10-16 10:34 ` |SUCCESS| pw157715 [PATCH v1 2/2] benchmark report for rte_memcpy 0-day Robot
2025-10-16 10:34 ` 0-day Robot
2025-10-16 10:43 ` |SUCCESS| pw157716-157715 [PATCH] [v1,2/2] benchmark report for rte_ dpdklab
2025-10-16 10:54 ` dpdklab
2025-10-16 11:05 ` dpdklab
2025-10-16 11:19 ` dpdklab
2025-10-16 11:26 ` dpdklab
2025-10-16 11:48 ` dpdklab
2025-10-16 11:48 ` dpdklab
2025-10-16 13:04 ` dpdklab
2025-10-16 13:49 ` dpdklab
2025-10-16 18:06 ` dpdklab
2025-10-16 18:22 ` dpdklab
2025-10-16 21:18 ` |WARNING| " dpdklab
2025-10-16 21:49 ` dpdklab
2025-10-16 21:50 ` dpdklab
2025-10-16 21:51 ` 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=68f0c1ea.170a0220.6ff2f.e8d7SMTPIN_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).