From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>,
Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw96403-96399 [PATCH] [v12, 6/6] maintainers: add for dmadev
Date: Fri, 30 Jul 2021 21:57:47 -0400 (EDT) [thread overview]
Message-ID: <20210731015747.BFF2488E71@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
Test-Label: iol-mellanox-Functional
Test-Status: FAILURE
http://dpdk.org/patch/96399
_Functional Testing issues_
Submitter: fengchengwen <fengchengwen@huawei.com>
Date: Thursday, July 29 2021 13:06:59
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:02e077f35dbc9821dfcb32714ad1096a3ee58d08
96403-96399 --> functional testing fail
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-4 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 1/1
Failed Tests:
- mtu_update
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 6/7
Failed Tests:
- mtu_update
- dynamic_config
- queue_start_stop
- scatter
- stats_checks
- unit_tests_mbuf
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/18023/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-07-31 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 1:57 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-31 2:40 dpdklab
2021-07-31 0:20 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=20210731015747.BFF2488E71@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 \
--cc=thomas@monjalon.net \
/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).