From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53616) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bchqZ-0005q6-Js for qemu-devel@nongnu.org; Wed, 24 Aug 2016 19:44:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bchqV-0008Sy-Fg for qemu-devel@nongnu.org; Wed, 24 Aug 2016 19:44:38 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:32956) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bchqO-0008QF-3M for qemu-devel@nongnu.org; Wed, 24 Aug 2016 19:44:35 -0400 Date: Wed, 24 Aug 2016 19:44:17 -0400 From: "Emilio G. Cota" Message-ID: <20160824234417.GA16295@flamenco> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] transient failure in the test-qht tests List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: QEMU Developers On Wed, Aug 24, 2016 at 21:39:01 +0100, Peter Maydell wrote: > So I encountered this test failure running 'make check' on > 32-bit ARM: > > MALLOC_PERTURB_=${MALLOC_PERTURB_:-$((RANDOM % 255 + 1))} gtester -k > --verbose -m=quick tests/test-qht > TEST: tests/test-qht... (pid=15763) > /qht/mode/default: OK > /qht/mode/resize: FAIL > GTester: last random seed: R02S08efd89fe4d862dd0191c13d5ce4d76e > (pid=16462) > FAIL: tests/test-qht > > The test suite passed on a rerun. > > Any ideas? I wonder whether malloc perturb had to do with the failure, because -ENOMEM is unlikely (I only see a few MB of peak mem usage for qht-test) However, I just ran qht-test under valgrind on an i686 machine, and it comes clean. I also brute-forced this to see if a particular perturb value would make it fail: for i in $(seq 0 255); do \ echo $i && \ MALLOC_PERTURB_=$i gtester -k --verbose -m=quick tests/test-qht \ --seed=R02S08efd89fe4d862dd0191c13d5ce4d76e || break; \ done I get no failures on both i686 and x86_64, with and without that --seed flag. Is there any chance of getting a core dump for the failure you encountered? Thanks, Emilio