From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134129 [PATCH] net/mlx5: zero encap UDP csum for IPv4 to
Date: Mon, 13 Nov 2023 04:55:42 -0800 (PST) [thread overview]
Message-ID: <65521cce.170a0220.cc7e2.7a6fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/134129
_Functional Testing PASS_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Monday, November 13 2023 07:29:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d677a3eb1b4e2d38c193fabd755dac30ee04c2df
134129 --> functional testing pass
Test environment and result as below:
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
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28345/
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-13 12:55 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 12:55 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-15 13:31 dpdklab
2023-11-15 12:47 dpdklab
2023-11-13 17:57 dpdklab
2023-11-13 17:07 dpdklab
2023-11-13 16:00 dpdklab
2023-11-13 14:01 dpdklab
2023-11-13 13:29 dpdklab
2023-11-13 13:17 dpdklab
2023-11-13 13:12 dpdklab
2023-11-13 13:10 dpdklab
2023-11-13 13:09 dpdklab
2023-11-13 13:09 dpdklab
2023-11-13 13:09 dpdklab
2023-11-13 13:09 dpdklab
2023-11-13 13:08 dpdklab
2023-11-13 13:08 dpdklab
2023-11-13 13:05 dpdklab
2023-11-13 13:02 dpdklab
2023-11-13 13:01 dpdklab
2023-11-13 13:01 dpdklab
2023-11-13 13:00 dpdklab
2023-11-13 13:00 dpdklab
2023-11-13 13:00 dpdklab
2023-11-13 12:59 dpdklab
2023-11-13 12:59 dpdklab
2023-11-13 12:59 dpdklab
2023-11-13 12:59 dpdklab
2023-11-13 12:59 dpdklab
2023-11-13 12:59 dpdklab
2023-11-13 12:59 dpdklab
2023-11-13 12:58 dpdklab
2023-11-13 12:58 dpdklab
2023-11-13 12:58 dpdklab
2023-11-13 12:58 dpdklab
2023-11-13 12:57 dpdklab
2023-11-13 12:57 dpdklab
2023-11-13 12:57 dpdklab
2023-11-13 12:57 dpdklab
2023-11-13 12:57 dpdklab
2023-11-13 12:57 dpdklab
2023-11-13 12:56 dpdklab
2023-11-13 12:56 dpdklab
2023-11-13 12:56 dpdklab
2023-11-13 12:55 dpdklab
2023-11-13 12:54 dpdklab
2023-11-13 12:53 dpdklab
2023-11-13 12:53 dpdklab
2023-11-13 12:51 dpdklab
2023-11-13 12:51 dpdklab
2023-11-13 12:49 dpdklab
2023-11-13 12:48 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=65521cce.170a0220.cc7e2.7a6fSMTPIN_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).