[Bug 39419] New: Fix the 'Failure running script in VM' errors

https://bugs.winehq.org/show_bug.cgi?id=39419

            Bug ID: 39419
           Summary: Fix the 'Failure running script in VM' errors
           Product: Wine-Testbot
           Version: unspecified
          Hardware: x86
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: unknown
          Assignee: wine-bugs(a)winehq.org
          Reporter: fgouget(a)codeweavers.com
      Distribution: ---

There are two very common 'boterror' types:

    Failure running script in VM: the "nc -q0 '10.42.42.133' '4242'"
    command returned 1
and
    Failure running script in VM: network read timed out
    (Connect:AgentVersion.h:0/9)

Both seem to correspond to a network issue and both seem to almost exclusively
and systematically happen with the w864 and w1064 VMs when running either a 32
or 64 bit WineTest job (i.e. running the full suite).

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.

[Bug 39419] Fix the 'Failure running script in VM' errors

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=39419

François Gouget <fgouget(a)codeweavers.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from François Gouget <fgouget(a)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.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.

[Bug 39419] Fix the 'Failure running script in VM' errors

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=39419

François Gouget <fgouget(a)codeweavers.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #2 from François Gouget <fgouget(a)codeweavers.com> ---
Closing.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.