From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw154554-154559 [PATCH] [v2,6/6] trace: add PMU
Date: Wed, 18 Jun 2025 08:38:12 -0700 (PDT) [thread overview]
Message-ID: <6852dd64.630a0220.104101.e15cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250618065618.4045910-7-tduszynski@marvell.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/154559
_Functional Testing PASS_
Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Wednesday, June 18 2025 06:56:18
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6890ee7ba76e92745d6c61b3b6b9d757ebaaa89d
154554-154559 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#231697
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/33447/
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-06-18 15:38 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250618065618.4045910-7-tduszynski@marvell.com>
2025-06-18 6:24 ` |SUCCESS| pw154554-154559 [PATCH v2 6/6] " qemudev
2025-06-18 6:28 ` qemudev
2025-06-18 6:57 ` |WARNING| pw154559 " checkpatch
2025-06-18 8:04 ` |FAILURE| " 0-day Robot
2025-06-18 11:29 ` |SUCCESS| pw154554-154559 [PATCH] [v2,6/6] " dpdklab
2025-06-18 11:35 ` dpdklab
2025-06-18 11:41 ` dpdklab
2025-06-18 11:44 ` dpdklab
2025-06-18 11:49 ` dpdklab
2025-06-18 12:18 ` dpdklab
2025-06-18 12:20 ` |PENDING| " dpdklab
2025-06-18 12:32 ` |FAILURE| " dpdklab
2025-06-18 12:41 ` |SUCCESS| " dpdklab
2025-06-18 12:42 ` dpdklab
2025-06-18 12:46 ` dpdklab
2025-06-18 12:53 ` |FAILURE| " dpdklab
2025-06-18 13:17 ` dpdklab
2025-06-18 13:23 ` dpdklab
2025-06-18 13:50 ` dpdklab
2025-06-18 14:43 ` |SUCCESS| " dpdklab
2025-06-18 15:38 ` dpdklab [this message]
2025-06-18 15:46 ` dpdklab
2025-06-18 15:49 ` dpdklab
2025-06-18 15:50 ` dpdklab
2025-06-18 16:25 ` dpdklab
2025-06-18 16:40 ` dpdklab
2025-06-18 17:14 ` |PENDING| " dpdklab
2025-06-18 17:54 ` |SUCCESS| " dpdklab
2025-06-18 18:20 ` dpdklab
2025-06-18 18:23 ` |FAILURE| " dpdklab
2025-06-18 18:31 ` dpdklab
2025-06-18 18:40 ` dpdklab
2025-06-18 18:43 ` |PENDING| " dpdklab
2025-06-18 18:48 ` |FAILURE| " dpdklab
2025-06-18 19:32 ` dpdklab
2025-06-18 19:34 ` dpdklab
2025-06-18 20:16 ` |SUCCESS| " dpdklab
2025-06-18 20:17 ` dpdklab
2025-06-18 20:17 ` dpdklab
2025-06-18 20:18 ` dpdklab
2025-06-18 20:18 ` dpdklab
2025-06-18 20:19 ` dpdklab
2025-06-18 20:20 ` dpdklab
2025-06-18 20:20 ` dpdklab
2025-06-18 20:32 ` |FAILURE| " 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=6852dd64.630a0220.104101.e15cSMTPIN_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).