qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PULL v2 0/7] Block patches


From: Marc-André Lureau
Subject: Re: [Qemu-devel] [PULL v2 0/7] Block patches
Date: Mon, 9 Nov 2015 10:09:37 -0500 (EST)

Hi

----- Original Message -----
> On 9 November 2015 at 12:51, Peter Maydell <address@hidden> wrote:
> > On 9 November 2015 at 10:08, Stefan Hajnoczi <address@hidden> wrote:
> >> The following changes since commit
> >> c4a7bf54e588ff2de9fba0898b686156251b2063:
> >>
> >>   Merge remote-tracking branch 'remotes/jnsnow/tags/ide-pull-request' into
> >>   staging (2015-11-07 19:55:15 +0000)
> >>
> >> are available in the git repository at:
> >>
> >>   git://github.com/stefanha/qemu.git tags/block-pull-request
> >>
> >> for you to fetch changes up to 84aa0140dd4f04f5d993f0db14c40da8d3de2706:
> >>
> >>   blockdev: acquire AioContext in hmp_commit() (2015-11-09 10:07:10 +0000)
> >>
> >> ----------------------------------------------------------------
> >>
> >> ----------------------------------------------------------------
> >
> > I got that intermittent ivshmem test failure again :-(
> >
> > ERROR:/home/petmay01/qemu/tests/ivshmem-test.c:345:test_ivshmem_server:
> > assertion failed (ret != 0): (0 != 0)
> >
> > I'll retry the tests...
> 
> Yep, worked fine second time, so applied.
> 
> Marc-André, can you look into why the ivshmem tests might be intermittently
> failing like this, please?

Is this with an slow or emulated host? It could be that the 5s timeout is not 
enough?

Alternatively, I think I could come up with a framework to put some kind of 
breakpoints in qemu, and wait until they happen. This would get rid of the 
timer.



reply via email to

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