|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [osstest test] 134608: regressions - trouble: broken/fail/pass
osstest service owner writes ("[osstest test] 134608: regressions - trouble:
broken/fail/pass"):
> flight 134608 osstest real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/134608/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-arm64-arm64-xl <job status> broken
> test-arm64-arm64-xl 4 host-install(4) broken REGR. vs.
> 133722
> test-arm64-arm64-examine 5 host-install broken REGR. vs.
> 133722
This appears to have been a stuck PDU relay on laxton0 :-/.
> test-amd64-amd64-libvirt-vhd 7 xen-boot fail REGR. vs.
> 133722
This is not expected. The logs are odd:
Apr 10 16:10:13.808014 [ 0.550515] PM-Timer failed consistency check
(0xffffff) - aborting.
...
Apr 10 16:10:13.916018 [ 0.550947] pci 0000:04:00.0: BAR 10: no space for
[mem size 0x00100000 64bit]
Apr 10 16:10:13.928007 [ 0.550953] pci 0000:04:00.0: BAR 10: failed to
assign [mem size 0x00100000 64bit]
and then it seems to get stuck. It's still up: the debug keys produce
register dumps etc. The host seems to be mostly working - ie this was
a one-off.
> test-amd64-amd64-xl-qcow2 17 guest-localmigrate/x10 fail REGR. vs.
> 133722
> test-amd64-amd64-examine 4 memdisk-try-append fail REGR. vs.
> 133722
These are the regressions I am expecting.
I'm going to see what the next flight (expected finish around 2-3pm UK
time) looks like.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |