Symptom¶
You get an error message like this:
FATAL ... test.js:13: AUT stopped responding
The Test Results view may also show a detail message like this:
Detail: The AUT 'aut_name' did not respond to network communication.
This error means Squish successfully hooked up to the AUT, but the AUT then did not reply to a Squish command within the Maximum Response Time. The default timeout is 300 seconds.
Possible causes¶
The AUT is hung or busy¶
If the AUT is busy, or is blocked for some other reason, the Maximum Response Time may pass without a reply, and Squish will report this error.
The Maximum Response Time is too short¶
If the AUT is working normally but takes longer than the Maximum Response Time to answer a command, Squish raises the same error. To increase the Maximum Response Time from the command line, for example to 600 seconds:
squishrunner --config setResponseTimeout 600
For Squish’s timeout settings and how to configure them, see Configurable timeouts .
Faulty time synchronization¶
Time synchronization clients like Windows's "Time Service" and VMware's "Synchronize Time" running at the same time on the same computer can cause the computer's time keeping to change in unexpected ways and thus cause this error.
This would usually occur with longer running tests.
Further symptoms:
The AUT is still responsive to manual user interaction, despite the error message.
The timestamp of subsequent log entries changes from the current time to a past time, as illustrated in this example:
LOG Fr 27. Mai 14:25:10 2011 test.js:12: Some output
FATAL Fr 27. Mai 14:20:41 2011 test.js:13: AUT stopped responding