From: Kevin Wolf <kwolf@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-block@nongnu.org, stefanha@redhat.com,
peter.maydell@linaro.org, berrange@redhat.com,
qemu-devel@nongnu.org
Subject: Re: [PATCH] tests/unit: Bump test-replication timeout to 45 seconds
Date: Thu, 25 Jan 2024 18:15:43 +0100 [thread overview]
Message-ID: <ZbKXP8YFSJU2yPh4@redhat.com> (raw)
In-Reply-To: <738b93ca-0049-4bd8-8702-52d295a5dd17@redhat.com>
Am 25.01.2024 um 18:05 hat Thomas Huth geschrieben:
> On 25/01/2024 17.58, Kevin Wolf wrote:
> > We're seeing timeouts for this test on CI runs (specifically for
> > ubuntu-20.04-s390x-all). It doesn't fail consistently, but even the
> > successful runs take about 27 or 28 seconds, which is not very far from
> > the 30 seconds timeout.
> >
> > Bump the timeout a bit to make failure less likely even on this CI host.
> >
> > Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> > ---
> > tests/unit/meson.build | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/tests/unit/meson.build b/tests/unit/meson.build
> > index 0659532122..db6398a0f4 100644
> > --- a/tests/unit/meson.build
> > +++ b/tests/unit/meson.build
> > @@ -175,7 +175,8 @@ slow_tests = {
> > 'test-aio-multithread' : 120,
> > 'test-crypto-block' : 300,
> > 'test-crypto-tlscredsx509': 45,
> > - 'test-crypto-tlssession': 45
> > + 'test-crypto-tlssession': 45,
> > + 'test-replication': 45,
> > }
> > foreach test_name, extra: tests
>
> I'd maybe even bump it to 60 seconds, just to be on the safe side.
Works for me, too. I can change it before sending a pull request.
> Anyway:
> Reviewed-by: Thomas Huth <thuth@redhat.com>
Thanks!
Kevin
prev parent reply other threads:[~2024-01-25 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 16:58 [PATCH] tests/unit: Bump test-replication timeout to 45 seconds Kevin Wolf
2024-01-25 17:05 ` Thomas Huth
2024-01-25 17:15 ` Kevin Wolf [this message]
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=ZbKXP8YFSJU2yPh4@redhat.com \
--to=kwolf@redhat.com \
--cc=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.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.