From: Aaron Conole <aconole@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Aaron Conole <aconole@redhat.com>,
Michael Santana <maicolgabriel@hotmail.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ci: increase unit test timeout
Date: Tue, 28 Jan 2020 15:53:16 -0500 [thread overview]
Message-ID: <f7tlfprl2v7.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: <20200128162854.3367823-1-ferruh.yigit@intel.com> (Ferruh Yigit's message of "Tue, 28 Jan 2020 16:28:54 +0000")
Ferruh Yigit <ferruh.yigit@intel.com> writes:
> Timeout multiplier was 3, which gives 30 seconds for unit test but still
> some unit test was timing out time to time and travis reporting false
> positive failures.
>
> Increasing the multiplier to 10, which makes timeout duration
> 100seconds.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
It's okay to me. I thought there was an effort to split out performance
part of this test from the functional part, but that seems to not have
gone anywhere.
Acked-by: Aaron Conole <aconole@redhat.com>
> .ci/linux-build.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.ci/linux-build.sh b/.ci/linux-build.sh
> index ccc3a7ccd..be3dc4940 100755
> --- a/.ci/linux-build.sh
> +++ b/.ci/linux-build.sh
> @@ -37,5 +37,5 @@ if [ "$AARCH64" != "1" ]; then
> fi
>
> if [ "$RUN_TESTS" = "1" ]; then
> - sudo meson test -C build --suite fast-tests -t 3
> + sudo meson test -C build --suite fast-tests -t 10
> fi
next prev parent reply other threads:[~2020-01-28 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 16:28 Ferruh Yigit
2020-01-28 18:39 ` Michael Santana
2020-01-28 20:53 ` Aaron Conole [this message]
2020-01-30 11:03 ` Thomas Monjalon
2020-01-30 15:35 ` Honnappa Nagarahalli
2020-01-31 15:44 ` Honnappa Nagarahalli
2020-02-05 18:47 ` David Marchand
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=f7tlfprl2v7.fsf@dhcp-25.97.bos.redhat.com \
--to=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=maicolgabriel@hotmail.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).