Re: [Xen-devel] [qemu-upstream-4.10-testing test] 136181: FAIL

[Anthony PERARD <anthony.perard@xxxxxxxxxx>]

On Wed, May 15, 2019 at 05:43:44PM +0000, osstest service owner wrote:
> flight 136181 qemu-upstream-4.10-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/136181/
> 
> Failures and problems with tests :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  build-arm64-pvops               <job status>                 broken  in 
> 134580
>  build-arm64                     <job status>                 broken  in 
> 134580
>  build-arm64-xsm                 <job status>                 broken  in 
> 134580
>  build-arm64-xsm            4 host-install(4) broken in 134580 REGR. vs. 
> 124921
>  build-arm64-pvops          4 host-install(4) broken in 134580 REGR. vs. 
> 124921
>  build-arm64                4 host-install(4) broken in 134580 REGR. vs. 
> 124921
> 
> Tests which are failing intermittently (not blocking):
>  test-amd64-amd64-xl-qcow2    17 guest-localmigrate/x10     fail pass in 
> 134580

Ian, I don't think I understand osstest's reasonning here.

Does the report says that the 'host-install' failure that happen a loong
time ago (with a different osstest) is blocking?
But that the -qcow2 test which now keeps failing isn't blocking?

Anyway, the *arm64* tests succeed, and the *qcow2 test keeps failing.
But the qcow2 issue seems to be a guest kernel thread failing to
suspend, so not a bug in qemu, but a regression the guest used for
testing, like in xen-* branches. So can you force push this?

Thanks,

-- 
Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel