From: Fabiano Rosas <farosas@suse.de>
To: Nabih Estefan <nabihestefan@google.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
peter.maydell@linaro.org, qemu-arm@nongnu.org,
qemu-devel@nongnu.org, lvivier@redhat.com, pbonzini@redhat.com,
roqueh@google.com, venture@google.com,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH] tests/qtest/sse-timer-test: Add watchdog reset to sse-timer test
Date: Fri, 13 Dec 2024 18:08:21 -0300 [thread overview]
Message-ID: <87frmrxpdm.fsf@suse.de> (raw)
In-Reply-To: <CA+QoejUUQK5L2LOgDPdK=kBgWgQQcvSMzXJ1zAiuwmoNwroPxg@mail.gmail.com>
Nabih Estefan <nabihestefan@google.com> writes:
> From what I can tell this is the same issue Thomas was looking at yes.
>
> I saw the failure on the master branch at the v9.2.0 tag (ae35f033) and just
> re-tested it against (83aaec1d) and still see it. I haven't seen it be an
> intermittent failure, it has failed 100% of the time that I have tested it when
> targeting arm-softmmu.
Could you please post the output of:
QTEST_LOG=1 QTEST_TRACE="sse_*" QTEST_QEMU_BINARY=./qemu-system-arm ./tests/qtest/sse-timer-test
Also your compiler version.
>
> However, you are right that with Phillippe's series on top of my change the
> bug is somehow re-introduced. Not sure what the protocol is here since
> neither patch has landed
I would like to figure out why this reproduces 100% for you (and some CI
job) and 0% for me and others. Once this is clear we can merge this
patch.
As for the other series let's leave the issues there to be discussed in
its own thread.
next prev parent reply other threads:[~2024-12-13 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 0:26 [PATCH] tests/qtest/sse-timer-test: Add watchdog reset to sse-timer test Nabih Estefan
2024-12-13 12:26 ` Thomas Huth
2024-12-13 18:48 ` Fabiano Rosas
2024-12-13 19:20 ` Nabih Estefan
2024-12-13 21:08 ` Fabiano Rosas [this message]
2024-12-13 21:09 ` Fabiano Rosas
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=87frmrxpdm.fsf@suse.de \
--to=farosas@suse.de \
--cc=lvivier@redhat.com \
--cc=nabihestefan@google.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=roqueh@google.com \
--cc=thuth@redhat.com \
--cc=venture@google.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.