From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: 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] 849770ce78a1b1a4871871feafbfcd9c204ea625
Date: Mon, 28 Nov 2022 07:02:52 -0500 (EST) [thread overview]
Message-ID: <20221128120252.6E76D3ECAD@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 676 bytes --]
_Functional Testing issues_
Branch: tags/v20.11
849770ce78a1b1a4871871feafbfcd9c204ea625 --> functional testing fail
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 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/22451/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-11-28 12:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 12:02 dpdklab [this message]
2022-11-28 12:14 dpdklab
2022-11-28 13:26 dpdklab
2022-11-29 7:13 dpdklab
2022-11-29 7:25 dpdklab
2022-11-29 7:35 dpdklab
2022-11-29 7:35 dpdklab
2022-11-29 9:06 dpdklab
2022-11-29 19:40 dpdklab
2022-11-29 19:48 dpdklab
2022-11-29 20:00 dpdklab
2022-11-30 19:23 dpdklab
2022-11-30 19:53 dpdklab
2022-11-30 20:09 dpdklab
2022-11-30 20:16 dpdklab
2022-11-30 20:24 dpdklab
2022-11-30 20:32 dpdklab
2022-11-30 20:39 dpdklab
2022-11-30 21:06 dpdklab
2022-11-30 21:15 dpdklab
2022-11-30 21:47 dpdklab
2022-11-30 22:01 dpdklab
2022-11-30 22:18 dpdklab
2022-11-30 22:19 dpdklab
2022-12-01 15:55 dpdklab
2022-12-02 14:25 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=20221128120252.6E76D3ECAD@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--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).