From: Andrew Jones <andrew.jones@linux.dev>
To: Nikos Nikoleris <nikos.nikoleris@arm.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.linux.dev,
Alexandru Elisei <alexandru.elisei@arm.com>,
thuth@redhat.com
Subject: Re: [kvm-unit-tests] arm/arm64: psci_cpu_on_test failures with tcg
Date: Fri, 23 Jun 2023 17:42:32 +0200 [thread overview]
Message-ID: <20230623-b5c6eb9ef3526abd6c45b30c@orel> (raw)
In-Reply-To: <20230607-a09e9dfd2719c01bd6b39df5@orel>
On Wed, Jun 07, 2023 at 08:49:36PM +0200, Andrew Jones wrote:
> On Wed, May 31, 2023 at 11:41:33AM +0100, Nikos Nikoleris wrote:
> > Hi,
> >
> > I noticed that in the latest master the psci_cpu_on_test fails randomly for
> > both arm and arm64 with tcg.
> >
> > If I do:
> >
> > $> for i in `seq 1 100`; do ACCEL=tcg MAX_SMP=8 ./run_tests.sh psci; done |
> > grep FAIL
> >
> > About 10 of the 100 runs fail for the arm and arm64 builds of the test. I
> > had a look and I am not sure I understand why. When I run the test with kvm,
> > I don't get any failures. Does anyone have an idea what could be causing
> > this?
> >
>
> I've also seen this failure on QEMU several times, but never investigated
> it. Now that the CI is running the tests under TCG the urgency of fixing
> it is higher, but we could also drop the psci test from the CI for now...
I just applied a patch[1] to drop the psci test from CI to arm/queue
because I was missing the nice green checkmark. We should certainly try
to figure out why it fails on tcg, though.
[1] https://gitlab.com/jones-drew/kvm-unit-tests/-/commit/bf4b759459e922b2e22c4281397a1857d4568186
Thanks,
drew
prev parent reply other threads:[~2023-06-23 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 10:41 [kvm-unit-tests] arm/arm64: psci_cpu_on_test failures with tcg Nikos Nikoleris
2023-06-06 14:20 ` Alexandru Elisei
2023-06-07 18:49 ` Andrew Jones
2023-06-23 15:42 ` Andrew Jones [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=20230623-b5c6eb9ef3526abd6c45b30c@orel \
--to=andrew.jones@linux.dev \
--cc=alexandru.elisei@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=nikos.nikoleris@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox