From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] 576842a59ab35979dc102535f59061fa3d6ea16b
Date: Fri, 25 Mar 2022 00:53:47 -0400 (EDT) [thread overview]
Message-ID: <20220325045347.903906D45F@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
_Functional Testing issues_
Branch: tags/v20.11
576842a59ab35979dc102535f59061fa3d6ea16b --> 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/19246/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-03-25 4:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 4:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-31 7:02 dpdklab
2022-03-30 7:49 dpdklab
2022-03-29 7:20 dpdklab
2022-03-28 6:51 dpdklab
2022-03-27 6:29 dpdklab
2022-03-26 7:31 dpdklab
2022-03-25 7:01 dpdklab
2022-03-25 1:29 dpdklab
2022-03-24 23:19 dpdklab
2022-03-24 20:51 dpdklab
2022-03-24 17:28 dpdklab
2022-03-24 16:48 dpdklab
2022-03-24 15:55 dpdklab
2022-03-23 5:26 dpdklab
2022-03-22 5:30 dpdklab
2022-03-21 5:20 dpdklab
2022-03-19 6:06 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=20220325045347.903906D45F@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=ajit.khaparde@broadcom.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--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).