From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137427-137430 [PATCH] [v3,4/4] net/mlx5: add support for
Date: Thu, 29 Feb 2024 15:30:33 -0800 (PST) [thread overview]
Message-ID: <65e11399.050a0220.13e71.4b23SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240228133312.474474-5-getelson@nvidia.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137430
_Functional Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Wednesday, February 28 2024 13:33:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f0cd4465b336362425eaae17fbaf7ac8f392da91
137427-137430 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.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-82
Compiler: gcc 11.4.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/29316/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-02-29 23:30 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240228133312.474474-5-getelson@nvidia.com>
2024-02-28 13:12 ` |SUCCESS| pw137427-137430 [PATCH v3 4/4] net/mlx5: add support for flow table resizing qemudev
2024-02-28 13:16 ` qemudev
2024-02-28 13:35 ` |SUCCESS| pw137430 " checkpatch
2024-02-28 14:47 ` |SUCCESS| pw137427-137430 [PATCH] [v3,4/4] net/mlx5: add support for dpdklab
2024-02-28 14:49 ` dpdklab
2024-02-28 14:50 ` dpdklab
2024-02-28 14:51 ` dpdklab
2024-02-28 14:52 ` dpdklab
2024-02-28 14:54 ` dpdklab
2024-02-28 14:54 ` dpdklab
2024-02-28 14:54 ` dpdklab
2024-02-28 14:55 ` dpdklab
2024-02-28 14:55 ` dpdklab
2024-02-28 15:09 ` dpdklab
2024-02-28 15:10 ` dpdklab
2024-02-28 15:10 ` dpdklab
2024-02-28 15:10 ` dpdklab
2024-02-28 15:11 ` dpdklab
2024-02-28 15:11 ` dpdklab
2024-02-28 15:11 ` dpdklab
2024-02-28 15:12 ` dpdklab
2024-02-28 15:12 ` dpdklab
2024-02-28 15:12 ` dpdklab
2024-02-28 15:12 ` dpdklab
2024-02-28 15:12 ` dpdklab
2024-02-28 15:12 ` dpdklab
2024-02-28 15:13 ` dpdklab
2024-02-28 15:13 ` dpdklab
2024-02-28 15:13 ` dpdklab
2024-02-28 15:14 ` dpdklab
2024-02-28 15:14 ` dpdklab
2024-02-28 15:14 ` dpdklab
2024-02-28 15:15 ` dpdklab
2024-02-28 15:15 ` dpdklab
2024-02-28 15:15 ` dpdklab
2024-02-28 15:15 ` dpdklab
2024-02-28 15:16 ` dpdklab
2024-02-28 15:16 ` dpdklab
2024-02-28 15:16 ` dpdklab
2024-02-28 15:16 ` dpdklab
2024-02-28 15:16 ` dpdklab
2024-02-28 15:16 ` dpdklab
2024-02-28 15:16 ` dpdklab
2024-02-28 15:17 ` dpdklab
2024-02-28 15:17 ` dpdklab
2024-02-28 15:17 ` dpdklab
2024-02-28 15:18 ` dpdklab
2024-02-28 15:18 ` dpdklab
2024-02-28 15:18 ` dpdklab
2024-02-28 15:20 ` dpdklab
2024-02-28 15:20 ` dpdklab
2024-02-28 15:21 ` dpdklab
2024-02-28 15:22 ` dpdklab
2024-02-28 15:22 ` dpdklab
2024-02-28 15:22 ` dpdklab
2024-02-28 15:24 ` dpdklab
2024-02-28 15:26 ` dpdklab
2024-02-28 15:27 ` dpdklab
2024-02-28 15:30 ` dpdklab
2024-02-28 15:34 ` dpdklab
2024-02-28 15:57 ` dpdklab
2024-02-28 18:00 ` dpdklab
2024-02-28 18:30 ` dpdklab
2024-02-28 20:52 ` dpdklab
2024-02-28 20:59 ` dpdklab
2024-02-29 12:36 ` dpdklab
2024-02-29 23:21 ` dpdklab
2024-02-29 23:22 ` dpdklab
2024-02-29 23:30 ` dpdklab [this message]
2024-02-29 23:35 ` dpdklab
2024-03-01 22:24 ` dpdklab
2024-03-01 22:51 ` dpdklab
2024-03-01 23: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=65e11399.050a0220.13e71.4b23SMTPIN_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).