From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152167-152168 [PATCH] [v2,2/2] devtools/dump-cpu-flags:
Date: Mon, 03 Mar 2025 14:44:30 -0800 (PST) [thread overview]
Message-ID: <67c630ce.c80a0220.2c4bd4.fb77SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1740779023-1274-3-git-send-email-andremue@linux.microsoft.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152168
_Functional Testing PASS_
Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Friday, February 28 2025 21:43:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fab31a03ba98e7457284df95dd9eef2223a4ccaa
152167-152168 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#215420
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 |
+----------------+--------+
| dynamic_queue | PASS |
+----------------+--------+
| rxtx_callbacks | PASS |
+----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32724/
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-03-03 22:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1740779023-1274-3-git-send-email-andremue@linux.microsoft.com>
2025-02-28 21:09 ` |SUCCESS| pw152167-152168 [PATCH v2 2/2] devtools/dump-cpu-flags: add tool to update CPU flags table qemudev
2025-02-28 21:13 ` qemudev
2025-02-28 21:44 ` |WARNING| pw152168 " checkpatch
2025-02-28 23:04 ` |SUCCESS| " 0-day Robot
2025-03-01 4:28 ` |SUCCESS| pw152167-152168 [PATCH] [v2,2/2] devtools/dump-cpu-flags: dpdklab
2025-03-01 4:29 ` dpdklab
2025-03-01 4:41 ` dpdklab
2025-03-01 4:42 ` dpdklab
2025-03-01 5:04 ` dpdklab
2025-03-01 5:05 ` dpdklab
2025-03-01 5:22 ` dpdklab
2025-03-01 5:31 ` dpdklab
2025-03-01 5:34 ` |PENDING| " dpdklab
2025-03-01 5:50 ` dpdklab
2025-03-01 5:59 ` |SUCCESS| " dpdklab
2025-03-01 6:02 ` dpdklab
2025-03-01 6:03 ` dpdklab
2025-03-01 6:24 ` |PENDING| " dpdklab
2025-03-01 6:48 ` |SUCCESS| " dpdklab
2025-03-01 7:02 ` dpdklab
2025-03-01 7:22 ` dpdklab
2025-03-01 8:00 ` dpdklab
2025-03-01 16:44 ` dpdklab
2025-03-01 23:34 ` dpdklab
2025-03-02 4:26 ` dpdklab
2025-03-02 4:27 ` dpdklab
2025-03-02 13:00 ` dpdklab
2025-03-03 22:44 ` 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=67c630ce.c80a0220.2c4bd4.fb77SMTPIN_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).