From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133388-133421 [PATCH] [v9,34/34] ml/cnxk: enable creatio
Date: Thu, 26 Oct 2023 07:21:36 -0700 (PDT) [thread overview]
Message-ID: <653a75f0.050a0220.f539e.f432SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/133421
_Functional Testing PASS_
Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Thursday, October 26 2023 12:43:43
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: master
CommitID:2a18c524c1b0cecaa1b1d944493874c1cea249b2
133388-133421 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 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/28090/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-26 14:21 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 14:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-28 7:07 dpdklab
2023-10-26 23:20 dpdklab
2023-10-26 23:13 dpdklab
2023-10-26 22:41 dpdklab
2023-10-26 15:48 dpdklab
2023-10-26 15:45 dpdklab
2023-10-26 15:45 dpdklab
2023-10-26 15:44 dpdklab
2023-10-26 15:30 dpdklab
2023-10-26 15:14 dpdklab
2023-10-26 15:14 dpdklab
2023-10-26 15:14 dpdklab
2023-10-26 15:13 dpdklab
2023-10-26 15:09 dpdklab
2023-10-26 15:08 dpdklab
2023-10-26 15:06 dpdklab
2023-10-26 15:04 dpdklab
2023-10-26 14:49 dpdklab
2023-10-26 14:49 dpdklab
2023-10-26 14:48 dpdklab
2023-10-26 14:47 dpdklab
2023-10-26 14:47 dpdklab
2023-10-26 14:46 dpdklab
2023-10-26 14:45 dpdklab
2023-10-26 14:44 dpdklab
2023-10-26 14:44 dpdklab
2023-10-26 14:43 dpdklab
2023-10-26 14:37 dpdklab
2023-10-26 14:36 dpdklab
2023-10-26 14:34 dpdklab
2023-10-26 14:33 dpdklab
2023-10-26 14:33 dpdklab
2023-10-26 14:33 dpdklab
2023-10-26 14:32 dpdklab
2023-10-26 14:25 dpdklab
2023-10-26 14:22 dpdklab
2023-10-26 14:22 dpdklab
2023-10-26 14:22 dpdklab
2023-10-26 14:22 dpdklab
2023-10-26 14:22 dpdklab
2023-10-26 14:22 dpdklab
2023-10-26 14:22 dpdklab
2023-10-26 14:22 dpdklab
2023-10-26 14:21 dpdklab
2023-10-26 14:21 dpdklab
2023-10-26 14:21 dpdklab
2023-10-26 14:20 dpdklab
2023-10-26 14:20 dpdklab
2023-10-26 14:20 dpdklab
2023-10-26 14:20 dpdklab
2023-10-26 14:20 dpdklab
2023-10-26 14:19 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=653a75f0.050a0220.f539e.f432SMTPIN_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).