From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152549-152559 [PATCH] [v5,11/11] member: use common AVX5
Date: Tue, 25 Mar 2025 09:37:57 -0700 (PDT) [thread overview]
Message-ID: <67e2dbe5.050a0220.24c26a.b61eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250325160254.1724560-12-bruce.richardson@intel.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152559
_Functional Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tuesday, March 25 2025 16:02:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fa3aca8a525decfd12bd5fa01ebc98789d5f7278
152549-152559 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#218957
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/32880/
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-03-25 16:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250325160254.1724560-12-bruce.richardson@intel.com>
2025-03-25 15:31 ` |SUCCESS| pw152549-152559 [PATCH v5 11/11] member: use common AVX512 build support qemudev
2025-03-25 15:36 ` qemudev
2025-03-25 16:06 ` |SUCCESS| pw152559 " checkpatch
2025-03-25 16:31 ` |SUCCESS| pw152549-152559 [PATCH] [v5,11/11] member: use common AVX5 dpdklab
2025-03-25 16:37 ` dpdklab [this message]
2025-03-25 16:48 ` |PENDING| " dpdklab
2025-03-25 16:50 ` |SUCCESS| " dpdklab
2025-03-25 16:53 ` dpdklab
2025-03-25 16:55 ` |PENDING| " dpdklab
2025-03-25 16:55 ` dpdklab
2025-03-25 16:57 ` |SUCCESS| " dpdklab
2025-03-25 16:58 ` dpdklab
2025-03-25 17:03 ` |FAILURE| " dpdklab
2025-03-25 17:04 ` dpdklab
2025-03-25 17:08 ` |SUCCESS| " dpdklab
2025-03-25 17:08 ` |PENDING| " dpdklab
2025-03-25 17:09 ` |FAILURE| " dpdklab
2025-03-25 17:13 ` dpdklab
2025-03-25 17:14 ` dpdklab
2025-03-25 17:16 ` dpdklab
2025-03-25 17:17 ` dpdklab
2025-03-25 17:20 ` |SUCCESS| " dpdklab
2025-03-25 17:21 ` dpdklab
2025-03-25 17:23 ` |SUCCESS| pw152559 [PATCH v5 11/11] member: use common AVX512 build support 0-day Robot
2025-03-25 17:24 ` |SUCCESS| pw152549-152559 [PATCH] [v5,11/11] member: use common AVX5 dpdklab
2025-03-25 17:25 ` |FAILURE| " dpdklab
2025-03-25 17:26 ` dpdklab
2025-03-25 17:28 ` |SUCCESS| " dpdklab
2025-03-25 17:36 ` |FAILURE| " dpdklab
2025-03-25 17:37 ` dpdklab
2025-03-25 17:39 ` dpdklab
2025-03-25 18:03 ` |SUCCESS| " dpdklab
2025-03-25 18:13 ` dpdklab
2025-03-25 18:14 ` dpdklab
2025-03-25 19:48 ` dpdklab
2025-03-25 20:57 ` dpdklab
2025-03-26 14:36 ` 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=67e2dbe5.050a0220.24c26a.b61eSMTPIN_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).