* vma-pthread unstable on aarch64 hardware
@ 2023-03-21 13:59 Alex Bennée
0 siblings, 0 replies; only message in thread
From: Alex Bennée @ 2023-03-21 13:59 UTC (permalink / raw)
To: Richard Henderson, Ilya Leoshkevich; +Cc: qemu-devel, Peter Maydell, qemu-arm
Date: Tue, 21 Mar 2023 13:48:20 +0000
User-agent: mu4e 1.9.22; emacs 29.0.60
Hi,
Chasing down some unstable check-tcg tests and I can get vma-pthread to
fail fairly reliably on the CI configuration ('../../configure'
'--enable-debug' '--static' '--disable-system' '--disable-pie') although
it seems to hold up on the default configuration ok.
retry.py -n 30 -c -- ./qemu-aarch64 ./tests/tcg/aarch64-linux-user/vma-pthread
...
**
ERROR:../../accel/tcg/cpu-exec.c:1019:cpu_exec_setjmp: assertion failed: (cpu == current_cpu)
Bail out! ERROR:../../accel/tcg/cpu-exec.c:1019:cpu_exec_setjmp: assertion failed: (cpu == current_cpu)
...
Results summary:
0: 29 times (96.67%), avg time 1.503 (0.00 varience/0.00 deviation)
-5: 1 times (3.33%), avg time 0.252 (0.00 varience/0.00 deviation)
Ran command 30 times, 29 passes
That said it might be responsible for some of the other tests that fail
when I do something like:
cd tests/tcg/aarch64-linux-user/
retry.py -n 30 --until -- make -f ../Makefile.target run
where I've seen random failures in float_convs, mte-1 and testthread
which make me wonder if this is some sort of toolchain/build config
issue?
Any ideas?
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-03-21 14:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-03-21 13:59 vma-pthread unstable on aarch64 hardware Alex Bennée
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).