Re: [Xen-devel] [xen-unstable test] 104187: trouble: blocked/broken

[Ian Jackson <ian.jackson@xxxxxxxxxxxxx>]

osstest service owner writes ("[xen-unstable test] 104187: trouble: 
blocked/broken"):
> flight 104187 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/104187/
> 
> Failures and problems with tests :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  build-armhf             3 host-install(3)        broken REGR. vs. 104181
>  build-armhf-pvops       3 host-install(3)        broken REGR. vs. 104181
>  build-armhf-xsm         3 host-install(3)        broken REGR. vs. 104181
>  build-i386-prev         3 host-install(3)        broken REGR. vs. 104181
>  build-amd64-oldkern     3 host-install(3)        broken REGR. vs. 104181
>  build-i386-xsm          3 host-install(3)        broken REGR. vs. 104181
>  build-amd64-prev        3 host-install(3)        broken REGR. vs. 104181
>  build-i386-pvops        3 host-install(3)        broken REGR. vs. 104181
>  build-amd64-xtf         3 host-install(3)        broken REGR. vs. 104181
>  build-i386-oldkern      3 host-install(3)        broken REGR. vs. 104181
>  build-amd64-pvops       3 host-install(3)        broken REGR. vs. 104181
>  build-amd64             3 host-install(3)        broken REGR. vs. 104181
>  build-amd64-xsm         3 host-install(3)        broken REGR. vs. 104181
>  build-i386              3 host-install(3)        broken REGR. vs. 104181

This is due to a Debian kernel update.  I have made the corresponding
change to osstest but I didn't want to force push it.

There will probably be a quite a few more reports like this but I
think it should sort itself out when the osstest self-push-gate passes
the update.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel