From: Kevin Wolf <kwolf@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] intermittent make check failure: "tcg_handle_interrupt: assertion failed: (qemu_mutex_iothread_locked())"
Date: Tue, 28 Feb 2017 21:52:47 +0100 [thread overview]
Message-ID: <20170228205247.GC4090@noname.redhat.com> (raw)
In-Reply-To: <CAFEAcA_KVG19uhPuBUNx4ySmebnL1Hit6=HUX9ug0FkBFMwasg@mail.gmail.com>
Am 28.02.2017 um 20:10 hat Peter Maydell geschrieben:
> I got a make check failure on aarch64 host running a sparc64 test:
Probably completely unrelated, but while we're at it...
For me, tests/vhost-user-test has been hanging for check-qtest-i386
occasionally in the past few days. Has anyone else seen this?
Kevin
next prev parent reply other threads:[~2017-02-28 20:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 19:10 [Qemu-devel] intermittent make check failure: "tcg_handle_interrupt: assertion failed: (qemu_mutex_iothread_locked())" Peter Maydell
2017-02-28 19:30 ` Thomas Huth
2017-02-28 21:28 ` Thomas Huth
2017-02-28 21:35 ` Mark Cave-Ayland
2017-02-28 22:07 ` Mark Cave-Ayland
2017-02-28 20:52 ` Kevin Wolf [this message]
2017-03-01 10:37 ` Dr. David Alan Gilbert
2017-03-01 11:36 ` Alex Bennée
2017-03-01 12:15 ` Mark Cave-Ayland
2017-03-01 12:41 ` Alex Bennée
2017-03-01 14:53 ` Mark Cave-Ayland
2017-03-01 15:19 ` Alex Bennée
2017-03-01 16:19 ` Mark Cave-Ayland
2017-03-01 18:33 ` Alex Bennée
2017-03-01 16:36 ` Peter Maydell
2017-03-01 18:17 ` Thomas Huth
2017-03-01 12:52 ` Peter Maydell
2017-03-01 18:27 ` [Qemu-devel] s390x " Thomas Huth
2017-03-01 18:35 ` Alex Bennée
2017-03-01 18:41 ` [Qemu-devel] xtensa " Thomas Huth
2017-03-01 20:32 ` Alex Bennée
2017-03-01 20:48 ` Peter Maydell
2017-03-02 11:39 ` [Qemu-devel] mips " Yongbok Kim
2017-03-02 12:57 ` Alex Bennée
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=20170228205247.GC4090@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 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).