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| pw124879-124880 [PATCH] [2/2] net/sfc: fix resetting mark in tunnel offload switch rules
Date: Sat, 11 Mar 2023 05:45:39 +0000 (UTC) [thread overview]
Message-ID: <20230311054539.62BE26011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/124880
_Functional Testing PASS_
Submitter: Ivan Malov <ivan.malov@arknetworks.am>
Date: Thursday, March 09 2023 04:28:42
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b15d75b2872efce397d827dac78692a919358302
124879-124880 --> 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
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.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/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25653/
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-11 5:45 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 5:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-13 6:34 dpdklab
2023-03-13 4:59 dpdklab
2023-03-12 16:44 dpdklab
2023-03-12 16:43 dpdklab
2023-03-12 16:15 dpdklab
2023-03-12 16:07 dpdklab
2023-03-12 16:05 dpdklab
2023-03-12 16:02 dpdklab
2023-03-12 15:51 dpdklab
2023-03-12 15:49 dpdklab
2023-03-12 15:47 dpdklab
2023-03-12 15:42 dpdklab
2023-03-12 15:40 dpdklab
2023-03-12 15:39 dpdklab
2023-03-12 15:34 dpdklab
2023-03-12 15:34 dpdklab
2023-03-12 15:34 dpdklab
2023-03-12 15:28 dpdklab
2023-03-12 14:55 dpdklab
2023-03-12 14:55 dpdklab
2023-03-12 14:53 dpdklab
2023-03-12 14:49 dpdklab
2023-03-12 14:46 dpdklab
2023-03-12 14:44 dpdklab
2023-03-12 14:43 dpdklab
2023-03-12 14:40 dpdklab
2023-03-12 14:34 dpdklab
2023-03-12 14:26 dpdklab
2023-03-12 14:24 dpdklab
2023-03-12 14:23 dpdklab
2023-03-12 6:02 dpdklab
2023-03-12 5:14 dpdklab
2023-03-12 4:41 dpdklab
2023-03-12 4:20 dpdklab
2023-03-11 7:20 dpdklab
2023-03-11 6:29 dpdklab
2023-03-11 6:17 dpdklab
2023-03-11 6:05 dpdklab
2023-03-11 6:00 dpdklab
2023-03-11 5:58 dpdklab
2023-03-11 5:56 dpdklab
2023-03-11 5:55 dpdklab
2023-03-11 5:55 dpdklab
2023-03-11 5:55 dpdklab
2023-03-11 5:50 dpdklab
2023-03-11 5:50 dpdklab
2023-03-11 5:49 dpdklab
2023-03-11 5:44 dpdklab
2023-03-11 5:38 dpdklab
2023-03-11 5:36 dpdklab
2023-03-11 5:31 dpdklab
2023-03-11 5:14 dpdklab
2023-03-11 4:55 dpdklab
2023-03-11 4:54 dpdklab
2023-03-11 4:53 dpdklab
2023-03-11 4:50 dpdklab
2023-03-11 4:47 dpdklab
2023-03-11 4:43 dpdklab
2023-03-11 4:41 dpdklab
2023-03-11 4:39 dpdklab
2023-03-11 4:35 dpdklab
[not found] <20230309042842.8709-2-ivan.malov@arknetworks.am>
2023-03-09 4:18 ` |SUCCESS| pw124879-124880 [PATCH 2/2] " qemudev
2023-03-09 4:22 ` qemudev
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=20230311054539.62BE26011D@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).