From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36261) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yd3xf-0005Pd-Hz for qemu-devel@nongnu.org; Tue, 31 Mar 2015 17:44:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yd3xa-0003zU-Iv for qemu-devel@nongnu.org; Tue, 31 Mar 2015 17:44:39 -0400 Received: from mx1.redhat.com ([209.132.183.28]:60551) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yd3xa-0003yK-BO for qemu-devel@nongnu.org; Tue, 31 Mar 2015 17:44:34 -0400 Message-ID: <551B153D.1080405@redhat.com> Date: Tue, 31 Mar 2015 17:44:29 -0400 From: John Snow MIME-Version: 1.0 References: <1427129798-21590-1-git-send-email-jsnow@redhat.com> <1427129798-21590-5-git-send-email-jsnow@redhat.com> <551B0A89.8060507@redhat.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 4/4] ahci-test: improve rw buffer patterns List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ed Maste Cc: Peter Maydell , qemu-devel On 03/31/2015 05:29 PM, Ed Maste wrote: > On 31 March 2015 at 16:58, John Snow wrote: >> >> which test case does it fail under? io_rw_simple is shared by a number of >> different tests. > > I'm not sure off hand how to run an individual test to confirm, but > the testrun output up to the failure is: > > LINK tests/spapr-phb-test > GTESTER check-qtest-aarch64 > GTESTER check-qtest-alpha > GTESTER check-qtest-arm > GTESTER check-qtest-cris > GTESTER check-qtest-i386 > blkdebug: Suspended request 'A' > blkdebug: Resuming request 'A' > ** > ERROR:tests/ahci-test.c:790:ahci_test_io_rw_simple: assertion failed > (memcmp(tx, rx, bufsize) == 0): (0xffffffffffffffff == 0x00000000) > GTester: last random seed: R02S181acd6574060796874e02dbdeb86199 > > Generally speaking I've only encountered build errors on FreeBSD, and > as long as it built the full test suite passed. > >> I suspect deeply that this test pattern has just unearthed an existing >> problem. > > Yeah, it's almost certainly just exposing the existing failure. > My apologies; Head into your build directory and try this: > make tests/ahci-test > export QTEST_QEMU_BINARY=i386-softmmu/qemu-system-i386 > export QTEST_QEMU_IMG=./qemu-img > ./tests/ahci-test This should show you which test in particular is failing. I have a hunch it will be the PIO, again... In the meantime, what is your setup? which release, what architecture? Thank you, --John