From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 472] failure in unit/self test
Date: Wed, 13 May 2020 08:48:16 +0000 [thread overview]
Message-ID: <bug-472-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=472
Bug ID: 472
Summary: failure in unit/self test
Product: DPDK
Version: 20.05
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: vipin.varghese@intel.com
Target Milestone: ---
DPDK:20.05-rc2
Linux:4.15.0-99-generic
GCC: Ubuntu 7.5.0-3ubuntu1~18.04
Distribution: Ubuntu 18.04.4 LTS
Steps:
1. fetch from git the right version of DPDK.
2. default build for `x86_64-native-linuxapp-gcc`
3. move to the directory `$RTE_SDK/app/test`
4. execute make
is the test cases (shared below) expected to fail
```
Cycles autotest: Fail [00m 01s][00m 02s]
EAL flags autotest: Fail [00m 02s][00m 05s]
Read/write lock autotest: Fail [Timeout] [00m 10s][00m 13s]
Alarm autotest: Fail [00m 00s][00m 37s]
PMD ring autotest: Fail [00m 00s][00m 55s]
Link bonding autotest: Fail [00m 00s][01m 11s]
Link bonding mode4 autotest: Fail [00m 00s][01m 12s]
Link bonding rssconf autotest:Fail [00m 00s][01m 12s]
```
I have 2 interfaces for DPDK
```
pci@0000:08:00.0 network Ethernet Controller X710 for 10GbE
SFP+
pci@0000:08:00.1 network Ethernet Controller X710 for 10GbE
SFP+
```
Is there documentation in sample application or getting started which calls out
what to ignore safely?
note:
a. based on suggestion from `David Marchand` opening a new bug
`https://bugs.dpdk.org/show_bug.cgi?id=471`.
b. requesting for document or release note update for test cases to safely
ignore.
c. requesting for document or guide update on recommend steps to run
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-05-13 8:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-472-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).