Bug 47 - Mempool performance autotest: Fail [Timeout]
Summary: Mempool performance autotest: Fail [Timeout]
Status: RESOLVED WONTFIX
Alias: None
Product: DPDK
Classification: Unclassified
Component: other (show other bugs)
Version: 18.02
Hardware: x86 Linux
: Normal normal
Target Milestone: ---
Assignee: reshma pattan
URL:
Depends on:
Blocks:
 
Reported: 2018-05-11 12:07 CEST by reshma pattan
Modified: 2018-09-14 12:26 CEST (History)
3 users (show)



Attachments
Discussions on the issue investigation (68.50 KB, application/x-ole-storage)
2018-09-14 12:25 CEST, jananeex.m.parthasarathy
Details

Description reshma pattan 2018-05-11 12:07:37 CEST
'Mempool performance autotest fails when run via sanity script "autotest.py"

DPDK version:
git repo -> latest dpdk-dpdk , last commit id: e2077a158e22451144d1b023f949f3232cfa62b3
OS: Fedora27, Centos7, FreeBSD, Ubuntu17.10
Compiler: GCC
32/64 bit compiler
Test Setup: Bare metal with Fedora27, Centos7, FreeBSD and Ubuntu17.10

Steps to reproduce
Run Sanity script as below, found "mempool_perf_autotest" fails.
./autotest.py ./build/app/test all

screen dump for the sanity:
Start mempool_perf: Success [00m 00s] 
('Mempool performance autotest: Fail [Timeout] [15m 00s]', '[28m 50s]')

Expected Result
Test should succeed with no errors
Comment 1 Anatoly Burakov 2018-07-16 13:05:57 CEST
Is the test still running, or are we waiting for wrong string?
Comment 2 Ajit Khaparde 2018-08-02 00:59:46 CEST
Reshma,
If the issue is still valid, can you respond to Anatoly's question?

Thanks
Ajit
Comment 3 reshma pattan 2018-08-02 11:29:51 CEST
Hi Ajit/Anatoly,

The issue appears when we run UT manually too. So the HCL team is agreed to work on the issue for DPDK 18.11 release.

Thanks,
Reshma
Comment 4 jananeex.m.parthasarathy 2018-09-14 12:25:17 CEST
Created attachment 12 [details]
Discussions on the issue investigation
Comment 5 jananeex.m.parthasarathy 2018-09-14 12:26:34 CEST
Hi All,

mempool_perf autotest works as expected functionally with status as Test OK.
The time taken for test run is approx 20 min which might not be reasonable for autotest.

Since these are performance related tests, the method to reduce its iterations/durations/tests may not be valid.
There are plans to remove perf tests from autotest.

Hence this bug can be closed as there is no issue in test as such.

Regards
M.P.Jananee

Note You need to log in before you can comment on or make changes to this bug.