From: dpdklab@iol.unh.edu
To: Lijuan Tu <lijuan.tu@intel.com>,
Test Report <test-report@dpdk.org>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Georgii Tkachuk <georgii.tkachuk@intel.com>,
Qian Xu <qian.q.xu@intel.com>
Cc: dpdk-test-reports@iol.unh.edu, "Namburu, Chandu-babu" <chandu@amd.com>
Subject: |FAILURE| pw104713 [PATCH] [v1] net/axgbe: use PCI root complex device to distinguish AMD hardware
Date: Fri, 26 Nov 2021 11:59:30 +0000 (UTC) [thread overview]
Message-ID: <20211126115930.821E8600AE@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
Test-Label: iol-intel-Functional
Test-Status: FAILURE
http://dpdk.org/patch/104713
_Functional Testing issues_
Submitter: Namburu, Chandu-babu <chandu@amd.com>
Date: Friday, November 26 2021 10:24:03
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:779279afa579570f4e62b708895fa52de1bee471
104713 --> functional testing fail
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 1/2
Failed Tests:
- scatter
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/20388/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-11-26 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 11:59 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-26 12:01 dpdklab
2021-11-26 11:47 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=20211126115930.821E8600AE@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=chandu@amd.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@intel.com \
--cc=georgii.tkachuk@intel.com \
--cc=lijuan.tu@intel.com \
--cc=qian.q.xu@intel.com \
--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).