From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136255-136254 [PATCH] [v5,2/2] test/devargs: add eth dev
Date: Thu, 01 Feb 2024 07:08:21 -0800 (PST) [thread overview]
Message-ID: <65bbb3e5.050a0220.9dda7.0e5cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/136254
_Functional Testing PASS_
Submitter: Harman Kalra <hkalra@marvell.com>
Date: Thursday, February 01 2024 10:02:19
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3178e37c65a676366f33f0bc56f49d9b26a06448
136255-136254 --> 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/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29013/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-01 15:08 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 15:08 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 17:17 dpdklab
2024-02-01 16:42 dpdklab
2024-02-01 16:32 dpdklab
2024-02-01 15:59 dpdklab
2024-02-01 15:59 dpdklab
2024-02-01 15:57 dpdklab
2024-02-01 15:55 dpdklab
2024-02-01 15:50 dpdklab
2024-02-01 15:45 dpdklab
2024-02-01 15:43 dpdklab
2024-02-01 15:42 dpdklab
2024-02-01 15:40 dpdklab
2024-02-01 15:36 dpdklab
2024-02-01 15:35 dpdklab
2024-02-01 15:34 dpdklab
2024-02-01 15:32 dpdklab
2024-02-01 15:28 dpdklab
2024-02-01 15:25 dpdklab
2024-02-01 15:23 dpdklab
2024-02-01 15:22 dpdklab
2024-02-01 15:19 dpdklab
2024-02-01 15:17 dpdklab
2024-02-01 15:17 dpdklab
2024-02-01 15:17 dpdklab
2024-02-01 15:16 dpdklab
2024-02-01 15:16 dpdklab
2024-02-01 15:15 dpdklab
2024-02-01 15:15 dpdklab
2024-02-01 15:15 dpdklab
2024-02-01 15:14 dpdklab
2024-02-01 15:14 dpdklab
2024-02-01 15:13 dpdklab
2024-02-01 15:12 dpdklab
2024-02-01 15:12 dpdklab
2024-02-01 15:12 dpdklab
2024-02-01 15:11 dpdklab
2024-02-01 15:11 dpdklab
2024-02-01 15:11 dpdklab
2024-02-01 15:10 dpdklab
2024-02-01 15:10 dpdklab
2024-02-01 15:10 dpdklab
2024-02-01 15:09 dpdklab
2024-02-01 15:08 dpdklab
2024-02-01 15:07 dpdklab
2024-02-01 15:07 dpdklab
2024-02-01 15:06 dpdklab
2024-02-01 15:06 dpdklab
2024-02-01 15:05 dpdklab
2024-02-01 15:04 dpdklab
2024-02-01 14:52 dpdklab
2024-02-01 14:48 dpdklab
2024-02-01 14:46 dpdklab
2024-02-01 14:46 dpdklab
2024-02-01 14:37 dpdklab
2024-02-01 14:25 dpdklab
2024-02-01 14:18 dpdklab
2024-02-01 14:18 dpdklab
2024-02-01 14:18 dpdklab
2024-02-01 14:18 dpdklab
2024-02-01 14:17 dpdklab
2024-02-01 14:16 dpdklab
2024-02-01 14:16 dpdklab
2024-02-01 14:11 dpdklab
2024-02-01 14:07 dpdklab
2024-02-01 14:04 dpdklab
2024-02-01 14:04 dpdklab
2024-02-01 13:57 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=65bbb3e5.050a0220.9dda7.0e5cSMTPIN_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).