All of 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 v2 1/1] support/testing: octave: increase test timeout
Date: Mon, 8 Aug 2022 23:08:46 +0200	[thread overview]
Message-ID: <20220808230846.6ff15f1b@windsurf> (raw)
In-Reply-To: <20220808201424.196176-1-ju.o@free.fr>

On Mon,  8 Aug 2022 22:14:24 +0200
Julien Olivain <ju.o@free.fr> wrote:

> Octave package test can occasionally fail due to timeout while testing
> some octave modules. This commit slightly increase the timeout value
> to reduce those failures.
> 
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> Changes v1 -> v2:
> - removed tweak of self.emulator.timeout_multiplier,
>   suggested by Thomas.
> ---
>  support/testing/tests/package/test_octave.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied to master, thanks.

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

  reply	other threads:[~2022-08-08 21:09 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 ` [Buildroot] [PATCH 1/2] support/testing: octave: increase test timeout Thomas Petazzoni via buildroot
2022-08-08 20:06   ` Julien Olivain
2022-08-08 20:14 ` [Buildroot] [PATCH v2 1/1] " Julien Olivain
2022-08-08 21:08   ` Thomas Petazzoni via buildroot [this message]
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=20220808230846.6ff15f1b@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 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.