From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: dev@dpdk.org, Jananee Parthasarathy <jananeex.m.parthasarathy@intel.com>
Cc: bugzilla@dpdk.org, "Pattan, Reshma" <reshma.pattan@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [Bug 62] Rawdev autotest fails
Date: Thu, 5 Jul 2018 14:49:39 +0530 [thread overview]
Message-ID: <8e96b8c1-f11b-d5fc-9973-153efa677a3e@nxp.com> (raw)
In-Reply-To: <bug-62-3@http.dpdk.org/tracker/>
On Friday 15 June 2018 04:52 PM, bugzilla@dpdk.org wrote:
> https://dpdk.org/tracker/show_bug.cgi?id=62
>
> Bug ID: 62
> Summary: Rawdev autotest fails
> Product: DPDK
> Version: 18.05
> Hardware: All
> OS: All
> Status: CONFIRMED
> Severity: normal
> Priority: Normal
> Component: other
> Assignee: dev@dpdk.org
> Reporter: reshma.pattan@intel.com
> Target Milestone: ---
>
> Rawdev autotest fails when run via sanity script "autotest.py"
>
> *DPDK version:
>
> *git repo -> latest dpdk-dpdk , last commit id:
> 2077a158e22451144d1b023f949f3232cfa62b3
> *OS: Fedora27, Centos7, Ubuntu17.10, FreeBSD
>
> *Compiler: GCC
>
> *32 bit compiler for Fedora27, Centos7, Ubuntu17.10
> *64 bit compiler for Fedora27, Centos7, Ubuntu17.10 and FreeBSD
>
> Test Setup: Bare metal with Ubuntu 17.10, Guest VM with centos 7 OS and
> Fedora27,FreeBSD
>
> Steps to reproduce
>
> Run Sanity script as below, found " Rawdev autotest: Fail "
> ./autotest.py ./build/app/test all
>
> screen dump for the sanity:
> Rawdev autotest: Fail [00m 00s]
>
> Expected Result
> Test should succeed with no errors
>
This issue occurs only when the patches from Jananee [1] are applied -
which are essentially adding many missing tests to autotest list.
Though the bug states that rawdev_autotest is failing, it is actually
some other issue in the autotest_data.py. In case the order of tests
just after 'event_eth_rx_adapter_autotest' is changed, the failure state
shifts to that test which comes just after 'event_eth_rx_adapter_autotest'.
On Master + patches from Jananee
--->8---
Event eth rx adapter autotest:Fail [Test returns Skipped] [00m 00s]
Rawdev autotest: Fail [00m 00s]
Kvargs autotest: Success [00m 00s]
Dump physmem: Skipped [Not Available] [00m 00s]
--->8---
With shuffling of tests case after 'event_eth_rx_adapter_autotest':
--->8---
Event eth rx adapter autotest:Fail [Test returns Skipped] [00m 00s]
Kvargs autotest: Fail [00m 00s]
Rawdev autotest: Success [00m 00s]
Dump physmem: Skipped [Not Available] [00m 00s]
--->8---
If I completely remove 'event_eth_rx_adapter_autotest', both kvargs and
devargs succeed.
--->8---
Kvargs autotest: Success [00m 00s]
Rawdev autotest: Success [00m 00s]
Dump physmem: Skipped [Not Available] [00m 00s]
--->8---
Though the data and its format in autotest_data.py looks fine to me, I
am not the best person for that - can someone give a hint what else
should I check?
Details also available in bugzilla [2].
[1] http://patches.dpdk.org/patch/40370/
[2] https://bugs.dpdk.org/show_bug.cgi?id=62
-
Shreyansh
prev parent reply other threads:[~2018-07-05 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 11:22 bugzilla
2018-07-05 9:19 ` Shreyansh Jain [this message]
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=8e96b8c1-f11b-d5fc-9973-153efa677a3e@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jananeex.m.parthasarathy@intel.com \
--cc=reshma.pattan@intel.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).