From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125035 [PATCH] mldev: fix identical code in conditional branches
Date: Sat, 11 Mar 2023 19:58:58 +0000 (UTC) [thread overview]
Message-ID: <20230311195858.1B6C06011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/125035
_Functional Testing PASS_
Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Saturday, March 11 2023 14:56:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b15d75b2872efce397d827dac78692a919358302
125035 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25693/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-11 19:59 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 19:58 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-13 21:04 dpdklab
2023-03-13 19:41 dpdklab
2023-03-13 4:55 dpdklab
2023-03-13 4:55 dpdklab
2023-03-13 4:23 dpdklab
2023-03-13 4:21 dpdklab
2023-03-13 4:19 dpdklab
2023-03-13 4:19 dpdklab
2023-03-13 4:15 dpdklab
2023-03-13 4:09 dpdklab
2023-03-13 4:08 dpdklab
2023-03-13 4:04 dpdklab
2023-03-13 3:51 dpdklab
2023-03-13 3:47 dpdklab
2023-03-13 3:39 dpdklab
2023-03-13 3:39 dpdklab
2023-03-13 2:59 dpdklab
2023-03-13 2:56 dpdklab
2023-03-13 2:55 dpdklab
2023-03-13 2:53 dpdklab
2023-03-13 2:50 dpdklab
2023-03-13 2:47 dpdklab
2023-03-13 2:46 dpdklab
2023-03-13 2:44 dpdklab
2023-03-13 2:41 dpdklab
2023-03-13 2:38 dpdklab
2023-03-13 2:37 dpdklab
2023-03-13 2:35 dpdklab
2023-03-12 17:04 dpdklab
2023-03-12 16:59 dpdklab
2023-03-12 15:52 dpdklab
2023-03-12 15:20 dpdklab
2023-03-11 21:33 dpdklab
2023-03-11 20:57 dpdklab
2023-03-11 20:49 dpdklab
2023-03-11 20:45 dpdklab
2023-03-11 20:44 dpdklab
2023-03-11 20:43 dpdklab
2023-03-11 20:42 dpdklab
2023-03-11 20:40 dpdklab
2023-03-11 20:38 dpdklab
2023-03-11 20:34 dpdklab
2023-03-11 20:34 dpdklab
2023-03-11 20:32 dpdklab
2023-03-11 20:31 dpdklab
2023-03-11 20:28 dpdklab
2023-03-11 20:24 dpdklab
2023-03-11 20:21 dpdklab
2023-03-11 20:16 dpdklab
2023-03-11 20:11 dpdklab
2023-03-11 20:06 dpdklab
2023-03-11 20:04 dpdklab
2023-03-11 20:04 dpdklab
2023-03-11 20:01 dpdklab
2023-03-11 19:57 dpdklab
2023-03-11 19:57 dpdklab
2023-03-11 19:50 dpdklab
2023-03-11 19:47 dpdklab
2023-03-11 19:46 dpdklab
[not found] <20230311145606.5523-1-syalavarthi@marvell.com>
2023-03-11 14:53 ` qemudev
2023-03-11 14:57 ` checkpatch
2023-03-11 14:57 ` qemudev
2023-03-11 17:19 ` 0-day Robot
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=20230311195858.1B6C06011D@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).