Skip to contentSkip to conversation

Rawdev autotest fails

Bug 62 [email protected] 2 participants 2 messages Jun 15, 2018 – Jul 5, 2018

lore
Share & tools
lore
#0 lore raw

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: [email protected]
          Reporter: [email protected]

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

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
#1 lore raw
Quoted 34 lines · On Friday 15 June 2018 04:52 PM, [email protected] 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: [email protected]
           Reporter: [email protected]

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

Quoted 9 lines

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