From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51873) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cinU1-0005a5-5m for qemu-devel@nongnu.org; Tue, 28 Feb 2017 14:30:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cinTy-0007QP-Uz for qemu-devel@nongnu.org; Tue, 28 Feb 2017 14:30:49 -0500 Received: from mx1.redhat.com ([209.132.183.28]:60460) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cinTy-0007QH-Ox for qemu-devel@nongnu.org; Tue, 28 Feb 2017 14:30:46 -0500 References: From: Thomas Huth Message-ID: <4b5d1228-fb99-6b8f-6f8b-bab42b84e7ce@redhat.com> Date: Tue, 28 Feb 2017 20:30:41 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] intermittent make check failure: "tcg_handle_interrupt: assertion failed: (qemu_mutex_iothread_locked())" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , QEMU Developers , =?UTF-8?Q?Alex_Benn=c3=a9e?= Cc: Richard Henderson , Mark Cave-Ayland , Artyom Tarasenko On 28.02.2017 20:10, Peter Maydell wrote: > I got a make check failure on aarch64 host running a sparc64 test: > > TEST: tests/prom-env-test... (pid=13573) > /sparc64/prom-env/sun4u: ** > ERROR:/home/pm215/qemu/translate-common.c:34:tcg_handle_interrupt: > assertion failed: (qemu_mutex_iothread_locked()) > Broken pipe > FAIL > GTester: last random seed: R02Sa5fa983185fe5e65cfb5b7fcb39ed3d1 > (pid=13579) > FAIL: tests/prom-env-test > > This is with commit 9514f2648ca05b3. > > It didn't reproduce on a rerun of 'make check' and it didn't > look like the merge in question was particularly relevant to > the failure, so I went ahead and pushed it to master. > > I'm (perhaps unfairly) assuming that this is fallout from MTTCG > landing. (prom-env-test is one of the handful of tests in > 'make check' that actually runs TCG code.) Maybe worth mentioning that the prom-env test for sparc64 has just been enabled a couple of commits ago (6b591ad613010f13). There was an issue with that test for the sparc64 target last year, but IIRC it only affected 32-bit hosts and has been fixed, so I think/hope this is a different issue now... Thomas