From: Kevin Traynor <ktraynor@redhat.com>
To: dpdklab@iol.unh.edu, Ajit Khaparde <ajit.khaparde@broadcom.com>,
Test Report <test-report@dpdk.org>,
ci@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Luca Boccassi <bluca@debian.org>
Subject: Re: |FAILURE| [GIT MASTER] 6ae8ba6b7aec5fbbce3449abe0c13c40d21561b9
Date: Thu, 24 Mar 2022 15:20:42 +0000 [thread overview]
Message-ID: <9def784c-8597-396d-5165-f9e67c6d3d36@redhat.com> (raw)
In-Reply-To: <20220324120036.20C5D6D45F@noxus.dpdklab.iol.unh.edu>
fyi, this report is 1 week old, just got it and some others for Broadcom
today. Maybe there is some queue being flushed or some server needs
attention etc?
Kevin.
On 24/03/2022 12:00, dpdklab@iol.unh.edu wrote:
> _Functional Testing issues_
>
> Branch: tags/v21.11
>
> 6ae8ba6b7aec5fbbce3449abe0c13c40d21561b9 --> functional testing fail
>
> Test environment and result as below:
>
> Ubuntu 20.04
> Kernel: 4.15.0-65-generic
> Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
> NIC: Broadcom Inc. brcm_57414 25000 Mbps
> Target: x86_64-native-linuxapp-gcc
> Fail/Total: 2/3
> Failed Tests:
> - mtu_update
> - scatter
>
>
> To view detailed results, visit:
> https://lab.dpdk.org/results/dashboard/tarballs/19169/
>
> UNH-IOL DPDK Community Lab
>
> To manage your email subscriptions, visit:
> https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next parent reply other threads:[~2022-03-24 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220324120036.20C5D6D45F@noxus.dpdklab.iol.unh.edu>
2022-03-24 15:20 ` Kevin Traynor [this message]
2022-03-24 18:42 ` [dpdklab] " Lincoln Lavoie
2022-03-25 15:15 ` Kevin Traynor
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=9def784c-8597-396d-5165-f9e67c6d3d36@redhat.com \
--to=ktraynor@redhat.com \
--cc=ajit.khaparde@broadcom.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=ci@dpdk.org \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=dpdklab@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).