All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	qemu-arm <qemu-arm@nongnu.org>,
	Richard Henderson <richard.henderson@linaro.org>
Subject: Re: snek testsuite breaks in 10.1 for qemu-system-arm on armhf
Date: Thu, 21 Aug 2025 15:16:17 +0100	[thread overview]
Message-ID: <877bywlpzi.fsf@draig.linaro.org> (raw)
In-Reply-To: <CAATJJ0K6coKjwwmkzaWP7dzQHLsEoL3rkU95T69rxZ6fdbnXqg@mail.gmail.com> (Christian Ehrhardt's message of "Thu, 21 Aug 2025 14:52:46 +0200")

Christian Ehrhardt <christian.ehrhardt@canonical.com> writes:

(adding qemu-arm and Richard to the CC)

> Hi,
> Debian and Ubuntu run the self tests of snek as integration tests like:
>
> `make SNEK_NATIVE=/usr/bin/snek SNEK_ARM=/usr/share/snek/snek-arm
> SNEK_RISCV=/usr/share/snek/snek-riscv -C test check`
>
> Those tests recently generated signal by failing in the arm emulation
> tests with `qemu-system-arm` - full log [1].
>
> ```
> 224s Running test pass-precedence.py.
> 224s     pass python3
> 224s     pass snek
> 224s pass-precedence.py:72 Syntax error at "".
> 224s     ***************** snek-arm fail *********************
> 224s     pass snek-riscv
> ```
>
> 14 tests failed, but all with quite similar signatures.
>
> But that only happens when executed on armhf, the other host
> architectures are all happy [2].
>
> I've separated the test and ran a git bisect on qemu 10.0 -> 10.1 as
> somewhere here is the trigger.
> That worked fine and identified this change [3].

This is:

  tcg: Convert deposit to TCGOutOpDeposit

  Reviewed-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
  Signed-off-by: Richard Henderson <richard.henderson@linaro.org>

> I must admit, I was able to debug it until here, but I can't see how
> these snek test failures could be caused by that change.
> And yes - arm emulation on an armhf platform isn't the most common
> scenario.

Are any of your other hosts 32 bit?

>
> I can't predict if there is anything wrong in snek which now is
> treated differently by qemu to trigger this or if snek is all fine and
> qemu broken something - Therefore I've also reported it to snek [4].
>
> The tracking of the initial finding in Ubuntu is here if you want to
> see more about how this commit was identified [5].
>
> [1]: https://autopkgtest.ubuntu.com/results/autopkgtest-questing/questing/armhf/s/snek/20250818_045020_246a4@/log.gz
> [2]: https://autopkgtest.ubuntu.com/packages/s/snek
> [3]: https://salsa.debian.org/qemu-team/qemu/-/commit/cf4905c03135f1181e86c618426f8d6c703b38c0
> [4]: https://github.com/keith-packard/snek/issues/103
> [5]: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2121124

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  parent reply	other threads:[~2025-08-21 14:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21 12:52 snek testsuite breaks in 10.1 for qemu-system-arm on armhf Christian Ehrhardt
2025-08-21 13:52 ` Stefan Hajnoczi
2025-08-21 14:16 ` Alex Bennée [this message]
2025-08-21 15:00   ` Christian Ehrhardt

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=877bywlpzi.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    /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.