[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [xen-4.9-testing test] 133881: regressions - FAIL
>>> On 19.03.19 at 01:39, <osstest-admin@xxxxxxxxxxxxxx> wrote: > flight 133881 xen-4.9-testing real [real] > http://logs.test-lab.xenproject.org/osstest/logs/133881/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-i386-libvirt-pair 22 guest-migrate/src_host/dst_host fail REGR. > vs. 132889 > test-amd64-amd64-libvirt-pair 22 guest-migrate/src_host/dst_host fail REGR. > vs. 132889 I've looked into these (and also the corresponding 4.8 one) before, without being able to spot anything that would provide some sort of hint to me as to what's actually going wrong. All I notice is error: Timed out during operation: cannot acquire state change lock But I have a hard time seeing how this can be a result of the changes under test (I assume the state change lock is a tools thing, and there are no pending tools changes). Yet judging from ... > Last test of basis 132889 2019-02-04 22:04:09 Z 42 days > Failing since 133147 2019-02-11 13:41:50 Z 35 days 24 attempts > Testing same since 133603 2019-03-05 18:49:35 Z 13 days 9 attempts ... this there's probably no hope anymore for this to go away all by itself. Could someone else please also look into these? I wonder if the failures are connected to the tests now running (stickily) on the merlots. The above time line also suggests that the problem started to appear with the version update, which can't possibly have caused a regression on its own. Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |