Re: test-aio-multithread assertion

[Peter Maydell <peter.maydell@linaro.org>]

On Thu, 5 Sep 2019 at 14:17, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Wed, 4 Sep 2019 at 12:50, Peter Maydell <peter.maydell@linaro.org> wrote:
> >
> > Hi; I've been seeing intermittently on the BSDs this assertion
> > running test-aio-multithread as part of 'make check':
> >
> > MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))}
> > tests/test-aio-multithread -m=quick -k --tap < /dev/null |
> > ./scripts/tap-drive
> > r.pl --test-name="test-aio-multithread"
> > PASS 1 test-aio-multithread /aio/multi/lifecycle
> > PASS 2 test-aio-multithread /aio/multi/schedule
> > ERROR - too few tests run (expected 5, got 2)
> > Assertion failed: (!qemu_lockcnt_count(&ctx->list_lock)), function
> > aio_ctx_finalize, file /home/qemu/qemu-test.kaRA0o/src/util/async.c,
> > line 283.
> > Abort trap (core dumped)
> > gmake: *** [/home/qemu/qemu-test.kaRA0o/src/tests/Makefile.include:905:
> > check-unit] Error 1
> >
> > Anybody got any ideas?
>
> Here's a different intermittent assertion on Netbsd from test-aio-multithread:
>
> MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))}
> tests/test-aio-multithread -m=quick
> -k --tap < /dev/null | ./scripts/tap-driver.pl
> --test-name="test-aio-multithread"
> PASS 1 test-aio-multithread /aio/multi/lifecycle
> PASS 2 test-aio-multithread /aio/multi/schedule
> assertion "QSLIST_EMPTY(&ctx->scheduled_coroutines)" failed: file
> "util/async.c", line 279, function "
> aio_ctx_finalize"
> ERROR - too few tests run (expected 5, got 2)

Just saw this QSLIST_EMPTY(&ctx->scheduled_coroutines) assertion
from FreeBSD as well, so it's still around as a definite
intermittent.

thanks
-- PMM