qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PULL 00/33] virtio, pc: fixes and features


From: Peter Maydell
Subject: Re: [Qemu-devel] [PULL 00/33] virtio, pc: fixes and features
Date: Mon, 10 Oct 2016 19:32:32 +0100

On 10 October 2016 at 15:13, Peter Maydell <address@hidden> wrote:
> On 10 October 2016 at 03:57, Michael S. Tsirkin <address@hidden> wrote:
>> The following changes since commit 48f592118ab42f83a1a7561c4bfd2b72a100f241:
>>
>>   bsd-user: fix FreeBSD build after d148d90e (2016-10-07 15:17:53 +0100)
>>
>> are available in the git repository at:
>>
>>   git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream
>>
>> for you to fetch changes up to dea651a95af6dad0997b840241a0bf6059d9a776:
>>
>>   intel-iommu: Check IOAPIC's Trigger Mode against the one in IRTE 
>> (2016-10-10 02:38:14 +0300)
>>
>> ----------------------------------------------------------------
>> virtio, pc: fixes and features
>>
>> more guest error handling for virtio devices
>> virtio migration rework
>> pc fixes
>>
>> Signed-off-by: Michael S. Tsirkin <address@hidden>
>
> This failed 'make check' on aarch64 host (everything else was ok):
>
> TEST: tests/pxe-test... (pid=11699)
>   /ppc64/pxe/virtio:                                                   **
> ERROR:/home/petmay01/qemu/tests/boot-sector.c:120:boot_sector_test:
> assertion failed (signature == SIGN
> ATURE): (0x00002020 == 0x0000dead)
> FAIL
> GTester: last random seed: R02S87a02de849c98998299177b1a4c7a31b
> (pid=19477)
>   /ppc64/pxe/spapr-vlan:                                               **
> ERROR:/home/petmay01/qemu/tests/boot-sector.c:120:boot_sector_test:
> assertion failed (signature == SIGN
> ATURE): (0x00002020 == 0x0000dead)
> FAIL
> GTester: last random seed: R02Sf9cf55ad239a137dd20d3085abf91524
> (pid=24055)
> FAIL: tests/pxe-test

Several subsequent test runs passed, so I'm inclined to suspect
this is not related to the pull request but is actually an
over-enthusiastic timeout and the build machine was heavily
loaded or something.

Anyway, I've pushed the merge to master.

thanks
-- PMM



reply via email to

[Prev in Thread] Current Thread [Next in Thread]