From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw89066-89072 [PATCH] [v4, 7/7] app/flow-perf: fix setting decap data for decap actions
Date: Sun, 14 Mar 2021 07:25:03 -0400 (EDT) [thread overview]
Message-ID: <20210314112503.247E988E65@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
Test-Label: iol-mellanox-Functional
Test-Status: FAILURE
http://dpdk.org/patch/89072
_Functional Testing issues_
Submitter: Wisam Jaddo <wisamm@nvidia.com>
Date: Sunday, March 14 2021 09:54:27
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1e28e842e08428ff5716fbe909bf5acd0365aaf6
89066-89072 --> functional testing fail
Test environment and result as below:
Ubuntu 18.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Mellanox ConnectX-5 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 1/4
Failed Tests:
- mac_filter
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/15926/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2021-03-14 11:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210314112503.247E988E65@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=dpdk-test-reports@dpdk.org \
--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).