From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138087 [PATCH] config/arm: add fallback march for Neover
Date: Thu, 07 Mar 2024 20:23:27 -0800 (PST) [thread overview]
Message-ID: <65ea92bf.810a0220.d0753.120aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240307080627.177-1-anoobj@marvell.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138087
_Functional Testing PASS_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Thursday, March 07 2024 08:06:27
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a454f84f715608ee709a4c6ba00edf2e4b62b69
138087 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29453/
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:[~2024-03-08 4:23 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240307080627.177-1-anoobj@marvell.com>
2024-03-07 7:43 ` |SUCCESS| pw138087 [PATCH] config/arm: add fallback march for Neoverse V2 qemudev
2024-03-07 7:48 ` qemudev
2024-03-07 8:08 ` checkpatch
2024-03-07 10:41 ` |SUCCESS| pw138087 [PATCH] config/arm: add fallback march for Neover dpdklab
2024-03-07 10:43 ` dpdklab
2024-03-07 10:43 ` dpdklab
2024-03-07 10:44 ` dpdklab
2024-03-07 10:45 ` dpdklab
2024-03-07 10:48 ` dpdklab
2024-03-07 10:49 ` dpdklab
2024-03-07 10:52 ` dpdklab
2024-03-07 11:04 ` dpdklab
2024-03-07 11:09 ` dpdklab
2024-03-07 11:09 ` dpdklab
2024-03-07 11:11 ` dpdklab
2024-03-07 11:11 ` dpdklab
2024-03-07 11:12 ` dpdklab
2024-03-07 11:20 ` dpdklab
2024-03-07 11:21 ` dpdklab
2024-03-07 11:21 ` dpdklab
2024-03-07 11:21 ` dpdklab
2024-03-07 11:27 ` dpdklab
2024-03-07 11:28 ` dpdklab
2024-03-07 11:43 ` dpdklab
2024-03-07 11:49 ` dpdklab
2024-03-07 11:49 ` dpdklab
2024-03-07 11:50 ` dpdklab
2024-03-07 11:52 ` dpdklab
2024-03-07 11:52 ` dpdklab
2024-03-07 11:53 ` dpdklab
2024-03-07 11:54 ` dpdklab
2024-03-07 11:55 ` dpdklab
2024-03-07 11:55 ` dpdklab
2024-03-07 11:56 ` dpdklab
2024-03-07 11:56 ` dpdklab
2024-03-07 11:56 ` dpdklab
2024-03-07 11:56 ` dpdklab
2024-03-07 11:57 ` dpdklab
2024-03-07 11:58 ` dpdklab
2024-03-07 12:04 ` dpdklab
2024-03-07 12:06 ` dpdklab
2024-03-07 12:06 ` dpdklab
2024-03-07 12:06 ` dpdklab
2024-03-07 12:06 ` dpdklab
2024-03-07 12:07 ` dpdklab
2024-03-07 12:07 ` dpdklab
2024-03-07 12:08 ` dpdklab
2024-03-07 12:09 ` dpdklab
2024-03-07 12:10 ` dpdklab
2024-03-07 12:10 ` dpdklab
2024-03-07 12:10 ` dpdklab
2024-03-07 12:11 ` dpdklab
2024-03-07 12:12 ` dpdklab
2024-03-07 12:12 ` dpdklab
2024-03-07 12:12 ` dpdklab
2024-03-07 12:12 ` dpdklab
2024-03-07 12:13 ` dpdklab
2024-03-07 12:14 ` dpdklab
2024-03-07 12:14 ` dpdklab
2024-03-07 12:14 ` dpdklab
2024-03-07 12:15 ` dpdklab
2024-03-07 12:15 ` dpdklab
2024-03-07 12:15 ` dpdklab
2024-03-07 12:24 ` dpdklab
2024-03-07 13:00 ` dpdklab
2024-03-07 13:11 ` dpdklab
2024-03-07 13:52 ` dpdklab
2024-03-07 19:09 ` dpdklab
2024-03-08 4:19 ` dpdklab
2024-03-08 4:23 ` dpdklab [this message]
2024-03-08 4:27 ` dpdklab
2024-03-08 4:31 ` dpdklab
2024-03-11 14:51 ` dpdklab
2024-03-11 16:52 ` 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=65ea92bf.810a0220.d0753.120aSMTPIN_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).