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
Subject: [dpdk-test-report] |FAILURE| [GIT MASTER] b1d36cf828771e28eb0130b59dcf606c2a0bc94d
Date: Mon, 16 Aug 2021 10:35:29 -0400 (EDT) [thread overview]
Message-ID: <20210816143529.6DD4189060@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
_Functional Testing issues_
Branch: tags/v20.11
b1d36cf828771e28eb0130b59dcf606c2a0bc94d --> 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: 1/3
Failed Tests:
- scatter
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/16271/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-08-16 14:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 14:35 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-17 4:31 dpdklab
2021-08-17 4:17 dpdklab
2021-08-16 15:22 dpdklab
2021-08-16 15:13 dpdklab
2021-08-16 15:08 dpdklab
2021-08-16 14:53 dpdklab
2021-08-16 14:31 dpdklab
2021-08-16 13:44 dpdklab
2021-08-16 13:38 dpdklab
2021-08-12 22:08 dpdklab
2021-08-12 21:14 dpdklab
2021-08-12 20:41 dpdklab
2021-08-12 19:41 dpdklab
2021-07-23 14:31 dpdklab
2021-07-23 14:28 dpdklab
2021-07-23 4:26 dpdklab
2021-07-21 12:51 dpdklab
2021-06-25 19:40 dpdklab
2021-06-25 17:11 dpdklab
2021-06-23 20:01 dpdklab
2021-06-23 14:35 dpdklab
2021-06-23 7:10 dpdklab
2021-06-23 4:19 dpdklab
2021-06-22 20:39 dpdklab
2021-06-17 23:16 dpdklab
2021-06-17 22:36 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=20210816143529.6DD4189060@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=ajit.khaparde@broadcom.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).