From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138089 [PATCH] [v3,1/1] app/graph: generate cmdline boil
Date: Thu, 07 Mar 2024 20:45:36 -0800 (PST) [thread overview]
Message-ID: <65ea97f0.050a0220.dfce8.6d38SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240307094009.3224478-1-skori@marvell.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138089
_Functional Testing PASS_
Submitter: Sunil Kumar Kori <skori@marvell.com>
Date: Thursday, March 07 2024 09:40:09
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8badf48d2100aa4f16b48f8006774febb65e47f3
138089 --> 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/29455/
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:45 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240307094009.3224478-1-skori@marvell.com>
2024-03-07 9:17 ` |SUCCESS| pw138089 [PATCH v3 1/1] app/graph: generate cmdline boilerplate qemudev
2024-03-07 9:22 ` qemudev
2024-03-07 9:42 ` checkpatch
2024-03-07 10:44 ` 0-day Robot
2024-03-07 11:08 ` |SUCCESS| pw138089 [PATCH] [v3,1/1] app/graph: generate cmdline boil dpdklab
2024-03-07 11:09 ` dpdklab
2024-03-07 11:10 ` dpdklab
2024-03-07 11:10 ` dpdklab
2024-03-07 11:11 ` dpdklab
2024-03-07 11:11 ` dpdklab
2024-03-07 11:12 ` dpdklab
2024-03-07 11:13 ` dpdklab
2024-03-07 11:20 ` dpdklab
2024-03-07 11:27 ` dpdklab
2024-03-07 11:29 ` dpdklab
2024-03-07 11:30 ` dpdklab
2024-03-07 11:31 ` dpdklab
2024-03-07 11:37 ` dpdklab
2024-03-07 11:42 ` dpdklab
2024-03-07 11:44 ` dpdklab
2024-03-07 11:44 ` dpdklab
2024-03-07 11:46 ` dpdklab
2024-03-07 11:47 ` dpdklab
2024-03-07 11:54 ` dpdklab
2024-03-07 12:05 ` dpdklab
2024-03-07 12:07 ` dpdklab
2024-03-07 12:07 ` dpdklab
2024-03-07 12:07 ` dpdklab
2024-03-07 12:07 ` dpdklab
2024-03-07 12:08 ` dpdklab
2024-03-07 12:08 ` dpdklab
2024-03-07 12:08 ` dpdklab
2024-03-07 12:09 ` dpdklab
2024-03-07 12:09 ` dpdklab
2024-03-07 12:09 ` dpdklab
2024-03-07 12:10 ` dpdklab
2024-03-07 12:10 ` dpdklab
2024-03-07 12:11 ` dpdklab
2024-03-07 12:11 ` dpdklab
2024-03-07 12:11 ` dpdklab
2024-03-07 12:12 ` dpdklab
2024-03-07 12:13 ` 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:14 ` dpdklab
2024-03-07 12:18 ` dpdklab
2024-03-07 12:18 ` dpdklab
2024-03-07 12:19 ` dpdklab
2024-03-07 12:19 ` dpdklab
2024-03-07 12:19 ` dpdklab
2024-03-07 12:20 ` dpdklab
2024-03-07 12:21 ` dpdklab
2024-03-07 12:21 ` dpdklab
2024-03-07 12:22 ` dpdklab
2024-03-07 12:26 ` dpdklab
2024-03-07 12:26 ` dpdklab
2024-03-07 12:27 ` dpdklab
2024-03-07 12:31 ` dpdklab
2024-03-07 12:47 ` dpdklab
2024-03-07 13:00 ` dpdklab
2024-03-07 13:01 ` dpdklab
2024-03-07 13:01 ` dpdklab
2024-03-07 13:02 ` dpdklab
2024-03-07 13:53 ` dpdklab
2024-03-07 14:50 ` dpdklab
2024-03-07 19:55 ` dpdklab
2024-03-08 4:37 ` dpdklab
2024-03-08 4:41 ` dpdklab
2024-03-08 4:45 ` dpdklab [this message]
2024-03-08 4:49 ` dpdklab
2024-03-11 17:42 ` dpdklab
2024-03-11 18:40 ` 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=65ea97f0.050a0220.dfce8.6d38SMTPIN_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).