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| pw125420 [PATCH] net/mlx5/hws: add check for modify-header actions
Date: Wed, 22 Mar 2023 11:35:54 +0000 (UTC) [thread overview]
Message-ID: <20230322113554.8B94B60121@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/125420
_Functional Testing PASS_
Submitter: Erez Shitrit <erezsh@nvidia.com>
Date: Wednesday, March 22 2023 10:16:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1a80f6062cf74e4b689b8b9a4f905a24efec527a
125420 --> functional testing pass
Test environment and result as below:
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/25830/
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-22 11:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 11:35 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-24 19:21 dpdklab
2023-03-23 22:17 dpdklab
2023-03-23 18:34 dpdklab
[not found] <20230322101621.642765-4-erezsh@nvidia.com>
2023-03-22 10:17 ` checkpatch
2023-03-22 12:59 ` 0-day Robot
2023-03-23 6:12 ` qemudev
2023-03-23 6:13 ` qemudev
2023-03-22 22:01 dpdklab
2023-03-22 13:42 dpdklab
2023-03-22 12:34 dpdklab
2023-03-22 12:24 dpdklab
2023-03-22 12:22 dpdklab
2023-03-22 12:09 dpdklab
2023-03-22 12:07 dpdklab
2023-03-22 11:58 dpdklab
2023-03-22 11:54 dpdklab
2023-03-22 11:50 dpdklab
2023-03-22 11:49 dpdklab
2023-03-22 11:41 dpdklab
2023-03-22 11:33 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=20230322113554.8B94B60121@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).