blinkbox/testswarm — pull request #31 by maciejblinkbox (2013-01-11 17:35:27+00:00)
Title: Cleanup action seems to be removing jobs that are in progress due to buggy server side timeout check

Cleanup action was triggered through curl and windows scheduled task every 5 minutes.
This was removing jobs currently running on devices. And was causing testswarm to reject results sent by devices later on.

Solution: fix the server side ping to update run_useragent.updated column in order to make Cleanup action to respect long running test executions.

Investigation:
To prove that the Cleanup action is the problem I disabled the scheduled job and have run the job which succeeded 3 times in a row and produced following timings:
- 301s http://battleship/testswarm/result/89618
- 298s http://battleship/testswarm/result/89576
- 307s http://battleship/testswarm/result/89570
So E2E tests from Catalogue\CategoriesFilter.feature were taking about 5 minutes on technika avtrex device.

Then I applied the code fix:
run_useragent.updated column is now updated every time new step execution is started ( by stepStart call to RunnerAction ).

Then I changed 5 minutes to 2 minutes interval for scheduled job, have run the Catalogue\CategoriesFilter.feature which succeeded straight away ( http://battleship/testswarm/result/89652 )

Solution worked.

TFS 2012 task 387