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| pw124616 [PATCH] [v4] bus: add platform bus
Date: Thu, 2 Mar 2023 04:33:21 +0000 (UTC) [thread overview]
Message-ID: <20230302043321.8FCE0601F7@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/124616
_Functional Testing PASS_
Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Wednesday, March 01 2023 19:59:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124616 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-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
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25578/
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-02 4:33 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 4:33 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-03 21:03 dpdklab
2023-03-03 21:03 dpdklab
2023-03-03 20:06 dpdklab
2023-03-03 20:04 dpdklab
2023-03-03 20:02 dpdklab
2023-03-03 20:00 dpdklab
2023-03-03 19:56 dpdklab
2023-03-03 19:52 dpdklab
2023-03-03 19:49 dpdklab
2023-03-03 19:48 dpdklab
2023-03-03 19:33 dpdklab
2023-03-03 19:33 dpdklab
2023-03-03 19:31 dpdklab
2023-03-03 19:21 dpdklab
2023-03-03 19:00 dpdklab
2023-03-03 18:58 dpdklab
2023-03-03 18:56 dpdklab
2023-03-03 18:54 dpdklab
2023-03-03 18:53 dpdklab
2023-03-03 18:50 dpdklab
2023-03-03 18:43 dpdklab
2023-03-03 18:41 dpdklab
2023-03-03 18:24 dpdklab
2023-03-03 18:19 dpdklab
2023-03-03 18:17 dpdklab
2023-03-03 18:17 dpdklab
2023-03-03 18:04 dpdklab
2023-03-03 17:53 dpdklab
2023-03-03 17:40 dpdklab
2023-03-03 17:39 dpdklab
2023-03-03 17:37 dpdklab
2023-03-03 17:30 dpdklab
2023-03-03 17:26 dpdklab
2023-03-03 17:24 dpdklab
2023-03-03 17:21 dpdklab
2023-03-03 17:20 dpdklab
2023-03-03 17:16 dpdklab
2023-03-03 17:12 dpdklab
2023-03-03 17:10 dpdklab
2023-03-03 17:04 dpdklab
2023-03-03 17:03 dpdklab
2023-03-03 16:59 dpdklab
2023-03-03 16:48 dpdklab
2023-03-03 16:47 dpdklab
2023-03-03 16:46 dpdklab
2023-03-03 16:41 dpdklab
2023-03-03 16:40 dpdklab
2023-03-03 16:32 dpdklab
2023-03-03 16:26 dpdklab
2023-03-03 16:22 dpdklab
2023-03-03 16:22 dpdklab
2023-03-03 16:01 dpdklab
2023-03-03 15:59 dpdklab
2023-03-03 15:57 dpdklab
2023-03-02 19:42 dpdklab
2023-03-02 19:11 dpdklab
2023-03-02 18:30 dpdklab
2023-03-02 17:23 dpdklab
2023-03-02 14:24 dpdklab
2023-03-02 14:01 dpdklab
2023-03-02 13:12 dpdklab
2023-03-02 13:05 dpdklab
2023-03-02 9:26 dpdklab
2023-03-02 9:14 dpdklab
2023-03-02 8:54 dpdklab
2023-03-02 8:22 dpdklab
2023-03-02 8:22 dpdklab
2023-03-02 8:09 dpdklab
2023-03-02 8:01 dpdklab
2023-03-02 7:52 dpdklab
2023-03-02 7:49 dpdklab
2023-03-02 7:36 dpdklab
2023-03-02 7:24 dpdklab
2023-03-02 7:11 dpdklab
2023-03-02 6:55 dpdklab
2023-03-02 6:43 dpdklab
2023-03-02 5:08 dpdklab
2023-03-02 4:55 dpdklab
2023-03-02 4:53 dpdklab
2023-03-02 4:46 dpdklab
2023-03-02 4:26 dpdklab
2023-03-02 4:06 dpdklab
2023-03-02 3:59 dpdklab
2023-03-02 3:39 dpdklab
2023-03-02 3:37 dpdklab
2023-03-02 3:31 dpdklab
2023-03-02 3:28 dpdklab
2023-03-02 3:24 dpdklab
2023-03-02 3:21 dpdklab
2023-03-02 3:20 dpdklab
2023-03-02 3:15 dpdklab
2023-03-02 3:15 dpdklab
2023-03-02 3:15 dpdklab
2023-03-02 3:11 dpdklab
2023-03-02 3:09 dpdklab
2023-03-02 3:05 dpdklab
2023-03-02 3:02 dpdklab
2023-03-02 3:01 dpdklab
2023-03-02 2:50 dpdklab
2023-03-02 2:49 dpdklab
2023-03-02 2:45 dpdklab
2023-03-02 2:40 dpdklab
2023-03-02 2:38 dpdklab
2023-03-02 2:37 dpdklab
2023-03-02 2:25 dpdklab
2023-03-02 2:22 dpdklab
2023-03-02 1:29 dpdklab
2023-03-02 1:15 dpdklab
2023-03-02 1:02 dpdklab
2023-03-02 0:48 dpdklab
[not found] <20230301195912.3835720-1-tduszynski@marvell.com>
2023-03-01 19:58 ` |SUCCESS| pw124616 [PATCH v4] " qemudev
2023-03-01 20:01 ` qemudev
2023-03-01 21:59 ` 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=20230302043321.8FCE0601F7@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).