From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137414 [PATCH] net/mlx5/hws: enable multiple integrity i
Date: Thu, 29 Feb 2024 14:15:05 -0800 (PST) [thread overview]
Message-ID: <65e101e9.050a0220.5d88f.729eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240228095055.3108270-1-michaelba@nvidia.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137414
_Functional Testing PASS_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Wednesday, February 28 2024 09:50:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fba0d7ac2d84dbe0e12b4989198640e14216762b
137414 --> functional testing pass
Test environment and result as below:
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
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29311/
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 22:15 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240228095055.3108270-1-michaelba@nvidia.com>
2024-02-28 9:28 ` |SUCCESS| pw137414 [PATCH] net/mlx5/hws: enable multiple integrity items qemudev
2024-02-28 9:33 ` qemudev
2024-02-28 9:52 ` checkpatch
2024-02-28 10:45 ` 0-day Robot
2024-02-28 12:12 ` |SUCCESS| pw137414 [PATCH] net/mlx5/hws: enable multiple integrity i dpdklab
2024-02-28 12:23 ` dpdklab
2024-02-28 12:27 ` dpdklab
2024-02-28 12:53 ` dpdklab
2024-02-28 12:55 ` dpdklab
2024-02-28 13:01 ` dpdklab
2024-02-28 13:01 ` dpdklab
2024-02-28 13:03 ` dpdklab
2024-02-28 13:08 ` dpdklab
2024-02-28 13:08 ` dpdklab
2024-02-28 13:10 ` dpdklab
2024-02-28 13:11 ` dpdklab
2024-02-28 13:11 ` dpdklab
2024-02-28 13:12 ` dpdklab
2024-02-28 13:13 ` dpdklab
2024-02-28 13:13 ` dpdklab
2024-02-28 13:17 ` dpdklab
2024-02-28 13:17 ` dpdklab
2024-02-28 13:18 ` dpdklab
2024-02-28 13:18 ` dpdklab
2024-02-28 13:18 ` dpdklab
2024-02-28 13:18 ` dpdklab
2024-02-28 13:19 ` dpdklab
2024-02-28 13:19 ` dpdklab
2024-02-28 13:19 ` dpdklab
2024-02-28 13:20 ` dpdklab
2024-02-28 13:20 ` dpdklab
2024-02-28 13:21 ` dpdklab
2024-02-28 13:23 ` dpdklab
2024-02-28 13:23 ` dpdklab
2024-02-28 13:23 ` dpdklab
2024-02-28 13:25 ` dpdklab
2024-02-28 13:26 ` dpdklab
2024-02-28 13:27 ` dpdklab
2024-02-28 13:27 ` dpdklab
2024-02-28 13:28 ` dpdklab
2024-02-28 13:28 ` dpdklab
2024-02-28 13:29 ` dpdklab
2024-02-28 13:31 ` dpdklab
2024-02-28 13:31 ` dpdklab
2024-02-28 13:32 ` dpdklab
2024-02-28 13:33 ` dpdklab
2024-02-28 13:33 ` dpdklab
2024-02-28 13:34 ` dpdklab
2024-02-28 13:34 ` dpdklab
2024-02-28 13:35 ` dpdklab
2024-02-28 13:35 ` dpdklab
2024-02-28 13:36 ` dpdklab
2024-02-28 13:36 ` dpdklab
2024-02-28 13:36 ` dpdklab
2024-02-28 13:40 ` dpdklab
2024-02-28 13:41 ` dpdklab
2024-02-28 13:42 ` dpdklab
2024-02-28 13:42 ` dpdklab
2024-02-28 13:43 ` dpdklab
2024-02-28 13:43 ` dpdklab
2024-02-28 13:43 ` dpdklab
2024-02-28 13:44 ` dpdklab
2024-02-28 13:45 ` dpdklab
2024-02-28 13:47 ` dpdklab
2024-02-28 14:37 ` dpdklab
2024-02-28 17:21 ` dpdklab
2024-02-28 19:11 ` dpdklab
2024-02-28 19:26 ` dpdklab
2024-02-29 9:53 ` dpdklab
2024-02-29 21:42 ` dpdklab
2024-02-29 21:50 ` dpdklab
2024-02-29 22:13 ` dpdklab
2024-02-29 22:15 ` dpdklab [this message]
2024-03-01 13:40 ` dpdklab
2024-03-01 14:34 ` dpdklab
2024-03-01 15:16 ` 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=65e101e9.050a0220.5d88f.729eSMTPIN_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).