From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Thomas Huth <thuth@redhat.com>
Subject: test harness hang running functional test
Date: Thu, 7 Nov 2024 16:09:42 +0000 [thread overview]
Message-ID: <CAFEAcA-4cf+yub8bsgtsdFOJD_9HziY3tekCN5s=+JcWEpw3Nw@mail.gmail.com> (raw)
I was trying to track down why one of the functional tests was
hanging, so I tried running it directly:
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1
QEMU_TEST_QEMU_BINARY=build/clang/qemu-system-loongarch64
PYTHONPATH=./build/clang/pyvenv:./python time
./build/clang/pyvenv/bin/python3
./tests/functional/test_loongarch64_virt.py
(This is with a QEMU built with the undefined-behaviour
sanitizer.)
Mostly this seems to succeed, but this time it's hung. Looking
at the process tree:
petmay01 3616444 0.0 0.0 4768 1124 pts/2 S+ 15:53 0:00
\_ time ./build/clang/pyvenv/bin/python3
./tests/functional/test_loongarch64_virt.py
petmay01 3616445 99.8 0.0 38480 23620 pts/2 R+ 15:53 13:20
\_ ./build/clang/pyvenv/bin/python3
./tests/functional/test_loongarch64_virt.py
petmay01 3616448 0.0 0.0 0 0 pts/2 Z+ 15:53 0:00
\_ [qemu-system-loo] <defunct>
The QEMU process itself has exited, but the test harness has
not yet noticed or reaped the zombie process. Instead it's sitting
there eating CPU. Presumably this is a bug in the test harness?
thanks
-- PMM
next reply other threads:[~2024-11-07 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 16:09 Peter Maydell [this message]
2024-11-07 16:18 ` test harness hang running functional test Peter Maydell
2024-11-11 10:37 ` Thomas Huth
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='CAFEAcA-4cf+yub8bsgtsdFOJD_9HziY3tekCN5s=+JcWEpw3Nw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--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;
as well as URLs for NNTP newsgroup(s).