qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>
Cc: "Pavel Dovgalyuk" <Pavel.Dovgalyuk@ispras.ru>,
	"Pavel Dovgalyuk" <pavel.dovgaluk@ispras.ru>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Cleber Rosa" <crosa@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Beraldo Leal" <bleal@redhat.com>
Subject: Re: [PULL 13/13] tests/avocado: remove skips from replay_kernel
Date: Thu, 11 Jan 2024 18:19:20 +0100	[thread overview]
Message-ID: <bef35657-d490-4db5-ad52-daba13c8234e@redhat.com> (raw)
In-Reply-To: <20240108151352.2199097-14-alex.bennee@linaro.org>

On 08/01/2024 16.13, Alex Bennée wrote:
> With the latest fixes for #2010 and #2013 these tests look pretty
> stable now. Of course the only way to be really sure is to run it in
> the CI infrastructure and see what breaks.
> 
> Acked-by: Pavel Dovgalyuk <Pavel.Dovgalyuk@ispras.ru>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Message-Id: <20231211091346.14616-14-alex.bennee@linaro.org>

The replay tests seem still to be very flaky, I'm now getting:

  https://gitlab.com/thuth/qemu/-/jobs/5910241580#L227
  https://gitlab.com/thuth/qemu/-/jobs/5910241593#L396

I'd suggest to revert this patch to disable them in the CI again.

  Thomas






  reply	other threads:[~2024-01-11 17:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 15:13 [PULL 00/13] replay fixes for replay_kernel Alex Bennée
2024-01-08 15:13 ` [PULL 01/13] tests/avocado: add a simple i386 replay kernel test Alex Bennée
2024-01-08 15:13 ` [PULL 02/13] tests/avocado: fix typo in replay_linux Alex Bennée
2024-01-08 15:13 ` [PULL 03/13] tests/avocado: modernise the drive args for replay_linux Alex Bennée
2024-01-08 15:13 ` [PULL 04/13] scripts/replay-dump: update to latest format Alex Bennée
2024-01-08 15:13 ` [PULL 05/13] scripts/replay_dump: track total number of instructions Alex Bennée
2024-01-08 15:13 ` [PULL 06/13] replay: remove host_clock_last Alex Bennée
2024-01-08 15:13 ` [PULL 07/13] replay: add proper kdoc for ReplayState Alex Bennée
2024-01-08 15:13 ` [PULL 08/13] replay: make has_unread_data a bool Alex Bennée
2024-01-08 15:13 ` [PULL 09/13] replay: introduce a central report point for sync errors Alex Bennée
2024-01-08 15:13 ` [PULL 10/13] replay/replay-char: use report_sync_error Alex Bennée
2024-01-08 15:13 ` [PULL 11/13] replay: stop us hanging in rr_wait_io_event Alex Bennée
2024-01-08 15:13 ` [PULL 12/13] chardev: force write all when recording replay logs Alex Bennée
2024-01-08 15:13 ` [PULL 13/13] tests/avocado: remove skips from replay_kernel Alex Bennée
2024-01-11 17:19   ` Thomas Huth [this message]
2024-01-12  9:35     ` Alex Bennée
2024-01-12 13:27     ` Alex Bennée
2024-01-09 14:23 ` [PULL 00/13] replay fixes for replay_kernel Peter Maydell
2024-01-09 14:24   ` Peter Maydell

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=bef35657-d490-4db5-ad52-daba13c8234e@redhat.com \
    --to=thuth@redhat.com \
    --cc=Pavel.Dovgalyuk@ispras.ru \
    --cc=alex.bennee@linaro.org \
    --cc=bleal@redhat.com \
    --cc=crosa@redhat.com \
    --cc=pavel.dovgaluk@ispras.ru \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wainersm@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).