>>> On 21.05.15 at 21:30, <osst...@xenbits.xen.org> wrote: > flight 56898 xen-4.5-testing real [real] > http://logs.test-lab.xenproject.org/osstest/logs/56898/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail REGR. vs. > 56728
This is recurring (i.e. presumably real), but none of the few changes under test appear to be related in any way. And going through the logs I can't spot anything suspicious either. Does anyone else have a clue? > test-amd64-amd64-rumpuserxen-amd64 15 > rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs. 56728 I suppose this (also recurring, and also seemingly unrelated to any of the commits under test) is due to device/vif = "" (n0,r49) device/vif/0 = "" (n49,r0) device/vif/0/backend = "/local/domain/0/backend/vif/49/0" (n49,r0) device/vif/0/backend-id = "0" (n49,r0) device/vif/0/state = "1" (n49,r0) device/vif/0/handle = "0" (n49,r0) rumpxenstack: xs_directory (device/vif/0/handle): Invalid argument but I have no idea what conclusion to draw from that as to where the problem might be. (As a side note - can anyone explain why elbling0---var-log-xen-console-guest-xenstorels.log.gz is gzip-ed twice?) > Tests which are failing intermittently (not blocking): > test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail pass in > 56821 > > Regressions which are regarded as allowable (not blocking): > test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like > 56728 It is interesting to see that these seem to intermittently fail, so perhaps the problem above is an older one... Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
