From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58935) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZsDcc-0004QA-Gn for qemu-devel@nongnu.org; Fri, 30 Oct 2015 13:37:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZsDcb-0005Fh-QK for qemu-devel@nongnu.org; Fri, 30 Oct 2015 13:37:50 -0400 Received: from mail-vk0-x233.google.com ([2607:f8b0:400c:c05::233]:34053) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZsDcb-0005Fc-NZ for qemu-devel@nongnu.org; Fri, 30 Oct 2015 13:37:49 -0400 Received: by vkgs66 with SMTP id s66so51943629vkg.1 for ; Fri, 30 Oct 2015 10:37:49 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <87wpu4h221.fsf@blackfin.pond.sub.org> References: <1446142165-24416-1-git-send-email-stefanha@redhat.com> <87wpu4h221.fsf@blackfin.pond.sub.org> From: Peter Maydell Date: Fri, 30 Oct 2015 17:37:30 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PULL 00/12] Block patches List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: QEMU Developers , Stefan Hajnoczi On 30 October 2015 at 14:19, Markus Armbruster wrote: > Peter Maydell writes: >> I get an error on 64-bit ARM running the ivshmem tests: >> >> TEST: tests/ivshmem-test... (pid=22948) >> /i386/ivshmem/single: OK >> /i386/ivshmem/pair: OK >> /i386/ivshmem/server: ** >> ERROR:/home/petmay01/qemu/tests/ivshmem-test.c:345:test_ivshmem_server: >> assertion failed (ret != 0): (0 != 0) >> FAIL >> GTester: last random seed: R02S51e68a84790014e86af5b8b7264d3e39 >> (pid=23709) >> /i386/ivshmem/hotplug: OK >> /i386/ivshmem/memdev: OK >> FAIL: tests/ivshmem-test >> >> Nothing obviously related in this patchset that would cause that, >> though... > > I've seen this, too, but throwing away my build tree made it go away, so > I blamed "make choking on stale build tree" syndrome. Perhaps it's an > intermittent ivshmem bug instead. I didn't do a make clean before successfully applying other pulls, so I think my money is on "intermittent ivshmem issue". I'll have another go with this one once I've finished the rest of the queue... thanks -- PMM