+Ilya (author of mentioned commit)
Hi, all
On 10/02/2026 05:14, Akihiko Odaki wrote:
On 2026/02/10 20:04, Jim MacArthur wrote:
On 2/9/26 12:03, Thomas Huth wrote:
From: Thomas Huth <[email protected]>
This reverts commit 55d98e3edeeb17dd8445db27605d2b34f4c3ba85.
The commit introduced a regression in the replay functional test
on alpha (tests/functional/alpha/test_replay.py), that causes CI
failures regularly. Thus revert this change until someone has
figured out what is going wrong here.
Buglink: https://gitlab.com/qemu-project/qemu/-/issues/3197
Signed-off-by: Thomas Huth <[email protected]>
---
I just hit this again in the CI:
https://gitlab.com/thuth/qemu/-/jobs/13018713844
... it's annoying, so I'd like to suggest to revert the offending
patch 'til someone fixed this.
Hi Thomas,
I am actively investigating this problem, but haven't made any
important progress so far. It's looking like a timing bug which is
annoying to track down. All I know for certain at the moment is that
faking some of the values returned by qemu_clock_get_ns to be
deterministic improves the failure rate, but does not remove it
entirely. I'm fine with this being reverted for now; we can add it
back in once we figure out what the true cause is.
Thanks for investigating this. Let's have the commit reverted until
there is some progress:
Reviewed-by: Akihiko Odaki <[email protected]>
After the quiescence commit, timeouts were the only regression, until
f098c32db48 ("target/s390x: Fix infinite loop during replay") when the
replay test began failing with error, too; maybe this serves as a
diagnostic trigger?
Yodel
