For most of our clients we've got a basic ant script that does a test deploy every night to make sure all the tests pass.
Occassionally, we'll get a REQUEST_RUNNING_TOO_LONG error. What's strange is that the time stamps it print don't seem like something that would generate an error. Take the output below for example, the deployment had only been running for 11 minutes (they typically take about an hour), and the test it had to stop had only been processing for 1s. What gives? Any idea what's causing this error?
/home/ec2-user/ant/auto_repos/example/build.xml:39: Failed to process the request successfully. Cause(UNKNOWN_EXCEPTION): Running test: Example, time spent on that test: 1236ms, total time spent running tests: 646005ms. Error: REQUEST_RUNNING_TOO_LONG: Your request was running for too long, and has been stopped.
Total time: 11 minutes 8 seconds
Additionally, with winter '16 these is happening pretty frequently, probably around 15% of test runs. With the automated test run it's not such a big deal, but waiting an hour doing a deployment to get this error is pretty frustrating (happened three times in a row last night).
Does anyone have info on why this is happening? Is this just a fact of life of the platform?