From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Nicholas Piggin" <npiggin@gmail.com>,
"Cédric Le Goater" <clg@kaod.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-ppc@nongnu.org
Subject: Re: [PATCH] tests/functional/test_ppc64_replay: Mark the e500 test as flaky
Date: Thu, 20 Mar 2025 09:32:01 +0000 [thread overview]
Message-ID: <Z9vgkaOJue2hHBUY@redhat.com> (raw)
In-Reply-To: <20250320065012.309520-1-thuth@redhat.com>
On Thu, Mar 20, 2025 at 07:50:12AM +0100, Thomas Huth wrote:
> The test_ppc64_e500 occasionally fails (it just hangs and finally times
> out). The same issue could also be reproduced with the former Avocado
> test already (especially if the host system is under heavy load), so
> it's not a new regression. It's very likely the issue that has been
> filed at https://gitlab.com/qemu-project/qemu/-/issues/2523 instead (e.g.
> I could not reproduce the issue in older commits before commit 578912ad),
> so use this URL for the reasoning in the the decorator.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> Here are some examples where the test failed:
> https://gitlab.com/thuth/qemu/-/jobs/9391454847
> https://gitlab.com/thuth/qemu/-/jobs/9457171828
> https://gitlab.com/thuth/qemu/-/jobs/9458371668
>
> tests/functional/test_ppc64_replay.py | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2025-03-20 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 6:50 [PATCH] tests/functional/test_ppc64_replay: Mark the e500 test as flaky Thomas Huth
2025-03-20 9:32 ` Daniel P. Berrangé [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=Z9vgkaOJue2hHBUY@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=clg@kaod.org \
--cc=npiggin@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--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 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).