From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 47] Mempool performance autotest: Fail [Timeout]
Date: Fri, 11 May 2018 10:07:37 +0000 [thread overview]
Message-ID: <bug-47-3@http.dpdk.org/tracker/> (raw)
https://dpdk.org/tracker/show_bug.cgi?id=47
Bug ID: 47
Summary: Mempool performance autotest: Fail [Timeout]
Product: DPDK
Version: 18.02
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: reshma.pattan@intel.com
Target Milestone: ---
'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
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-05-11 10:07 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-47-3@http.dpdk.org/tracker/ \
--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).