Re: [Xen-devel] [xen-4.9-testing test] 133666: regressions - FAIL

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 10.03.19 at 12:38, <osstest-admin@xxxxxxxxxxxxxx> wrote:
> flight 133666 xen-4.9-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/133666/ 
> 
> 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

Both of the above as well as the similar failing test occurred on the merlots,
showing

error: Timed out during operation: cannot acquire state change lock

in the logs. Is this just coincidence?

>  test-amd64-amd64-xl-qemuu-ws16-amd64 16 guest-localmigrate/x10 fail REGR. 
> vs. 132889

Looks to be the Windows-reboots-while-being-migrated issue again:

libxl: debug: libxl_dom_suspend.c:348:suspend_common_wait_guest_check: Domain 
19:guest we were suspending has shut down with unexpected reason code 1
libxl: debug: libxl_event.c:673:libxl__ev_xswatch_deregister: watch w=0x163eb60 
wpath=@releaseDomain token=3/0: deregister slotnum=3
xc: error: save callback suspend() failed: 0: Internal error
xc: error: Save failed (0 = Success): Internal error

Iirc previously we've simply waited long enough for this eventually
not happening during one of the retry flights. I still think something
needs to be done about this.

Jan



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