Re: make check-functional failures with --enable-rust: unsafe precondition(s) violated: NonNull::new_unchecked

["Philippe Mathieu-Daudé" <philmd@linaro.org>]

On 7/3/25 19:24, Peter Maydell wrote:
> I noticed that 'make check-functional' for arm targets doesn't all
> pass when QEMU is built with --enable-rust:
> 
> 11/46 qemu:func-thorough+func-aarch64-thorough+thorough /
> func-aarch64-aarch64_virt            TIMEOUT         720.03s   killed
> by signal 15 SIGTERM
>   9/46 qemu:func-thorough+func-arm-thorough+thorough /
> func-arm-arm_tuxrun                      ERROR            51.71s
> exit status 1
> 30/46 qemu:func-thorough+func-arm-thorough+thorough /
> func-arm-arm_vexpress                    ERROR             1.62s
> exit status 1
> 44/46 qemu:func-thorough+func-arm-thorough+thorough /
> func-arm-arm_replay                      TIMEOUT          90.02s
> killed by signal 15 SIGTERM
> 
> The first of these is the virt/gpu breakage that's not Rust related.
> 
> tuxrun fails because of a Rust panic, though:

[...]

> Is this a known issue ? (I'm using git commit 98c7362b1efe.)
> 
> Here's the RUST_BACKTRACE=1 version:


> (side note: should we set RUST_BACKTRACE=1 for our
> make check/check-functional infra? it would probably be better
> to capture the backtrace in the logfiles rather than needing
> the user to re-run by hand, especially for the CI case.)

I agree, and Stefan also suggested that:
https://lore.kernel.org/qemu-devel/CAJSP0QWJ=qkA2Bzih7nGq5K=YrJRqUOt85RAGL=mj3MEjAW6ug@mail.gmail.com/