From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| pw133748-133758 [PATCH] [11/11] drivers: enable multiple P
Date: Thu, 02 Nov 2023 00:04:52 -0700 (PDT) [thread overview]
Message-ID: <65434a14.050a0220.58e99.8db7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/133758
_Functional Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Thursday, November 02 2023 02:23:21
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:71f9da6691c49d0dfcf088dce5e99c488af0eb7e
133748-133758 --> functional testing pass
Test environment and result as below:
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 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
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/28191/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-02 7:04 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 7:04 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-02 17:52 dpdklab
2023-11-02 10:16 dpdklab
2023-11-02 8:38 dpdklab
2023-11-02 7:12 dpdklab
2023-11-02 7:07 dpdklab
2023-11-02 6:45 dpdklab
2023-11-02 6:42 dpdklab
2023-11-02 6:38 dpdklab
2023-11-02 6:38 dpdklab
2023-11-02 6:24 dpdklab
2023-11-02 6:23 dpdklab
2023-11-02 6:22 dpdklab
2023-11-02 6:21 dpdklab
2023-11-02 6:10 dpdklab
2023-11-02 6:10 dpdklab
2023-11-02 6:09 dpdklab
2023-11-02 6:09 dpdklab
2023-11-02 6:08 dpdklab
2023-11-02 6:07 dpdklab
2023-11-02 6:07 dpdklab
2023-11-02 6:07 dpdklab
2023-11-02 6:06 dpdklab
2023-11-02 6:06 dpdklab
2023-11-02 6:06 dpdklab
2023-11-02 6:01 dpdklab
2023-11-02 6:00 dpdklab
2023-11-02 5:59 dpdklab
2023-11-02 5:59 dpdklab
2023-11-02 5:59 dpdklab
2023-11-02 5:58 dpdklab
2023-11-02 5:58 dpdklab
2023-11-02 5:58 dpdklab
2023-11-02 5:56 dpdklab
2023-11-02 5:56 dpdklab
2023-11-02 5:55 dpdklab
2023-11-02 5:54 dpdklab
2023-11-02 5:53 dpdklab
2023-11-02 5:53 dpdklab
2023-11-02 5:51 dpdklab
2023-11-02 5:51 dpdklab
2023-11-02 5:50 dpdklab
2023-11-02 5:49 dpdklab
2023-11-02 5:48 dpdklab
2023-11-02 4:58 dpdklab
2023-11-02 4:54 dpdklab
2023-11-02 4:51 dpdklab
2023-11-02 4:19 dpdklab
2023-11-02 4:18 dpdklab
2023-11-02 4:18 dpdklab
2023-11-02 4:17 dpdklab
2023-11-02 4:17 dpdklab
2023-11-02 4:17 dpdklab
2023-11-02 4:11 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=65434a14.050a0220.58e99.8db7SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@amd.com \
--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).