From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134748-134769 [PATCH] [v1,23/23] net/mlx5: add support f
Date: Mon, 04 Dec 2023 13:05:58 -0800 (PST) [thread overview]
Message-ID: <656e3f36.050a0220.13561.15e1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/134769
_Functional Testing PASS_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Sunday, December 03 2023 11:25:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c858f006d1f7161986c88847259a400d8f80d81b
134748-134769 --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28511/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-04 21:06 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 21:05 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-04 23:31 dpdklab
2023-12-04 23:09 dpdklab
2023-12-04 22:56 dpdklab
2023-12-04 22:23 dpdklab
2023-12-04 22:21 dpdklab
2023-12-04 22:21 dpdklab
2023-12-04 22:18 dpdklab
2023-12-04 22:03 dpdklab
2023-12-04 21:59 dpdklab
2023-12-04 21:33 dpdklab
2023-12-04 21:30 dpdklab
2023-12-04 21:29 dpdklab
2023-12-04 21:29 dpdklab
2023-12-04 21:26 dpdklab
2023-12-04 20:49 dpdklab
2023-12-04 20:45 dpdklab
2023-12-04 20:44 dpdklab
2023-12-04 20:20 dpdklab
2023-12-04 20:19 dpdklab
2023-12-04 20:19 dpdklab
2023-12-04 20:18 dpdklab
2023-12-04 20:14 dpdklab
2023-12-04 20:14 dpdklab
2023-12-04 20:14 dpdklab
2023-12-04 20:13 dpdklab
2023-12-04 20:13 dpdklab
2023-12-04 20:10 dpdklab
2023-12-04 20:10 dpdklab
2023-12-04 20:09 dpdklab
2023-12-04 20:09 dpdklab
2023-12-04 20:09 dpdklab
2023-12-04 20:09 dpdklab
2023-12-04 20:08 dpdklab
2023-12-04 20:08 dpdklab
2023-12-04 20:08 dpdklab
2023-12-04 20:07 dpdklab
2023-12-04 20:07 dpdklab
2023-12-04 20:06 dpdklab
2023-12-04 20:03 dpdklab
2023-12-04 20:03 dpdklab
2023-12-04 20:02 dpdklab
2023-12-04 20:02 dpdklab
2023-12-04 20:02 dpdklab
2023-12-04 20:01 dpdklab
2023-12-04 20:01 dpdklab
2023-12-04 20:00 dpdklab
2023-12-04 19:56 dpdklab
2023-12-04 19:56 dpdklab
2023-12-04 19:52 dpdklab
2023-12-04 19:51 dpdklab
2023-12-04 19:51 dpdklab
2023-12-04 19:51 dpdklab
2023-12-04 19:49 dpdklab
2023-12-04 19:47 dpdklab
2023-12-04 19:36 dpdklab
2023-12-04 19:04 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=656e3f36.050a0220.13561.15e1SMTPIN_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).