https://bugs.winehq.org/show_bug.cgi?id=39419
François Gouget fgouget@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #1 from François Gouget fgouget@codeweavers.com --- It seems that nowadays this only happens when a Windows VM crashes. In such a case it is normal for the connection to break down.
Also such errors are better handled. The TestBot will actually rerun the test to rule out a temporary network issue. It will also check whether the VM is still powered on or not. And in cases where it is sure the test is not the culprit (e.g. if the issue happens when sending the test binary), the task is requeued and no error is reported on that test.
There may be cases where a runaway Windows Update caused Windows to reboot at an importune time (see also bug 47800). These would highly depend on how long ago the VM was booted. Normally Windows Update is always disabled... except on Windows 10 where this is not reliable. So if there are cases where Windows Update is causing trouble a bug should be filed against the specific VM.
So I think this issue is essentially solved.