On Tue, Apr 14, 2015 at 11:57:35AM +0200, Kevin Wolf wrote:
[snip]
> --- a/block/vhdx.c
> +++ b/block/vhdx.c
> @@ -1285,7 +1285,7 @@ static coroutine_fn int vhdx_co_writev(BlockDriverState
> *bs, int64_t sector_num,
> iov2.iov_base = qemu_blockalign(bs, iov2.iov_len);
>
Am 15.04.2015 um 11:47 schrieb Kevin Wolf:
> Am 15.04.2015 um 11:34 hat Andreas Färber geschrieben:
>> Am 15.04.2015 um 11:26 schrieb Kevin Wolf:
>>> Am 15.04.2015 um 06:53 hat Jeff Cody geschrieben:
On Tue, Apr 14, 2015 at 11:57:35AM +0200, Kevin Wolf wrote:
> Am 11.04.2015 um 05:41 hat A
Am 15.04.2015 um 11:34 hat Andreas Färber geschrieben:
> Am 15.04.2015 um 11:26 schrieb Kevin Wolf:
> > Am 15.04.2015 um 06:53 hat Jeff Cody geschrieben:
> >> On Tue, Apr 14, 2015 at 11:57:35AM +0200, Kevin Wolf wrote:
> >>> Am 11.04.2015 um 05:41 hat Andreas Färber geschrieben:
> Hi,
>
>
Am 15.04.2015 um 11:26 schrieb Kevin Wolf:
> Am 15.04.2015 um 06:53 hat Jeff Cody geschrieben:
>> On Tue, Apr 14, 2015 at 11:57:35AM +0200, Kevin Wolf wrote:
>>> Am 11.04.2015 um 05:41 hat Andreas Färber geschrieben:
Hi,
001 seems to hang for -qcow (or is not reasonably "quick": >5 m
Am 15.04.2015 um 06:53 hat Jeff Cody geschrieben:
> On Tue, Apr 14, 2015 at 11:57:35AM +0200, Kevin Wolf wrote:
> > Am 11.04.2015 um 05:41 hat Andreas Färber geschrieben:
> > > Hi,
> > >
> > > 001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
> > >
> > > 033 is failing for -vhdx
On Tue, Apr 14, 2015 at 11:57:35AM +0200, Kevin Wolf wrote:
> Am 11.04.2015 um 05:41 hat Andreas Färber geschrieben:
> > Hi,
> >
> > 001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
> >
> > 033 is failing for -vhdx.
> >
> > (Note that `make check-block` only tests -qcow2, so d
Am 11.04.2015 um 05:41 hat Andreas Färber geschrieben:
> Hi,
>
> 001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
>
> 033 is failing for -vhdx.
>
> (Note that `make check-block` only tests -qcow2, so didn't uncover
> either of them.)
>
> Given a failing test, am I seeing corr
Am 13.04.2015 um 17:29 schrieb John Snow:
> On 04/10/2015 11:41 PM, Andreas Färber wrote:
>> Hi,
>>
>> 001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
>>
>
> I assume this was a one-off and you cannot reproduce it reliably.
No, I could reproduce it both locally and in our buil
On 11/04/2015 16:33, Andreas Färber wrote:
> 067 is failing for -qcow2 on ppc64 (no $QEMU_PROG => qemu-system-ppc64).
> Seems to hang after the below output.
It really needs a PC machine, it seems.
Paolo
On 04/10/2015 11:41 PM, Andreas Färber wrote:
Hi,
001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
I assume this was a one-off and you cannot reproduce it reliably.
Do you have any data on what call it might have hung on?
033 is failing for -vhdx.
(Note that `make che
Am 11.04.2015 um 05:41 schrieb Andreas Färber:
> Hi,
>
> 001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
>
> 033 is failing for -vhdx.
067 is failing for -qcow2 on ppc64 (no $QEMU_PROG => qemu-system-ppc64).
Seems to hang after the below output.
Andreas
$ tests/qemu-iotests
Hi,
001 seems to hang for -qcow (or is not reasonably "quick": >5 min).
033 is failing for -vhdx.
(Note that `make check-block` only tests -qcow2, so didn't uncover
either of them.)
Given a failing test, am I seeing correctly that there is no command
line option to skip this one failing test? -
12 matches
Mail list logo
