From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 758] Timeouts in fast tests service_autotest, red_autotest
Date: Fri, 16 Jul 2021 07:04:54 +0000 [thread overview]
Message-ID: <bug-758-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=758
Bug ID: 758
Summary: Timeouts in fast tests service_autotest, red_autotest
Product: DPDK
Version: 20.11
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: christian.ehrhardt@canonical.com
Target Milestone: ---
Hi,
as part of the CI we are running the fast-tests after every build in Debian and
Ubuntu [1][2][3]. As part of this we happened to see that in this environment
some issues occur.
This issue is about 2 tests which seem to be sized to "just fit" but often (not
always) exceed their 30 second timeout if run in busy environments.
50/58 DPDK:fast-tests / service_autotest TIMEOUT 30.01s
and
25/59 DPDK:fast-tests / red_autotest TIMEOUT 30.01s
Detailed logs at [4][5].
I wanted to ask if we could bump the timeout of those which are close to hit
the timeout on slow systems OR if we should remove them from fast tests?
[1]: https://packaging.ubuntu.com/html/auto-pkg-test.html
[2]: https://autopkgtest.ubuntu.com/
[3]: https://ci.debian.net/
[4]:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/d/dpdk/20210712_095836_75b36@/log.gz
[5]:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/d/dpdk/20210712_094652_75b36@/log.gz
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-07-16 7:04 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-758-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.