Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] support/testing: octave: increase test timeout
Date: Sun, 7 Aug 2022 19:22:29 +0200	[thread overview]
Message-ID: <20220807192229.0d697a6c@windsurf> (raw)
In-Reply-To: <20220807165538.850640-1-ju.o@free.fr>

Hello Julien,

On Sun,  7 Aug 2022 18:55:37 +0200
Julien Olivain <ju.o@free.fr> wrote:

> Octave package test can occasionally fail due to timeout.
> This commit slightly increase timeout values to reduce those failures.
> 
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
>  support/testing/tests/package/test_octave.py | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/support/testing/tests/package/test_octave.py b/support/testing/tests/package/test_octave.py
> index 82a70e09c2..2d808e0cca 100644
> --- a/support/testing/tests/package/test_octave.py
> +++ b/support/testing/tests/package/test_octave.py
> @@ -34,6 +34,7 @@ class TestOctave(infra.basetest.BRTest):
>                             kernel=kern,
>                             kernel_cmdline=["console=ttyAMA0"],
>                             options=["-M", "virt", "-cpu", "cortex-a57", "-m", "512M", "-initrd", img])
> +        self.emulator.timeout_multiplier *= 2

Thanks for the patch.

I know a few other tests are tweaking timeout_multiplier, but I think
it's wrong. The idea of timeout_multiplier is that it's defined on the
command line, when running the tests, to indicate that you're running
on a "slow" machine that requires a timeout factor.

Tests should only tweak the timeout value, and the timeout_multiplier
will be applied to these timeouts.

So I think we should remove these tweaks on timeout_multiplier in test
cases, rather than add more.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-08-07 17:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-07 16:55 [Buildroot] [PATCH 1/2] support/testing: octave: increase test timeout Julien Olivain
2022-08-07 16:55 ` [Buildroot] [PATCH 2/2] package/octave: bump to version 7.2.0 Julien Olivain
2022-08-07 17:32   ` Thomas Petazzoni via buildroot
2022-08-07 17:22 ` Thomas Petazzoni via buildroot [this message]
2022-08-08 20:06   ` [Buildroot] [PATCH 1/2] support/testing: octave: increase test timeout Julien Olivain
2022-08-08 20:14 ` [Buildroot] [PATCH v2 1/1] " Julien Olivain
2022-08-08 21:08   ` Thomas Petazzoni via buildroot
2022-09-14 22:19 ` [Buildroot] [PATCH 1/2] " Peter Korsgaard

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=20220807192229.0d697a6c@windsurf \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=thomas.petazzoni@bootlin.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