Completed, yet timed out

[jzaefferer]

I got this from a run of a the resizable test suite in jQuery UI:

~/dev/jquery-ui [git:drag-resize-relative-position+?] $ browserstack-runner
Launching 12 workers
[Windows 8, Chrome 32.0] Completed in 3890 milliseconds. 232 of 232 passed, 0 failed.
[Windows 8, Chrome 32.0] Screenshot: https://s3.amazonaws.com/testautomation/205cc92c471c3b479cc6788ab39bcc47b7dd9d3f/js-screenshot-1396366499.png
[Windows 8.1, Firefox 27.0] Completed in 2534 milliseconds. 232 of 232 passed, 0 failed.
[Windows 8.1, Firefox 27.0] Screenshot: https://s3.amazonaws.com/testautomation/411709057a8b4b6f73380570fe2f240965b4b91e/js-screenshot-1396366506.png
[Windows 8, Firefox 28.0] Completed in 2939 milliseconds. 232 of 232 passed, 0 failed.
[Windows 8, Firefox 28.0] Screenshot: https://s3.amazonaws.com/testautomation/4b9a29143a5b2c7741b89ec16f3c65f45742a443/js-screenshot-1396366588.png
[Windows 7, Opera 19.0] Completed in 14457 milliseconds. 232 of 232 passed, 0 failed.
[Windows 7, Opera 19.0] Screenshot: https://s3.amazonaws.com/testautomation/18fa0a004f56c3828e93df42ed1db9aa348ad5ac/js-screenshot-1396366597.png
[OS X Mavericks, Safari 7.0] Completed in 1255 milliseconds. 232 of 232 passed, 0 failed.
[Windows 7, Ie 9.0] Completed in 44 milliseconds. 0 of 0 passed, 0 failed.
[OS X Mavericks, Safari 7.0] Screenshot: https://s3.amazonaws.com/testautomation/c90a6de932909ffe308c0ae62502752a84632650/js-screenshot-1396366638.png
[Windows 7, Ie 9.0] Screenshot: https://s3.amazonaws.com/testautomation/2d29d9b8250688dcdf0c1069a8c0879d7404c697/js-screenshot-1396366641.png
[Windows 8.1, Opera 20.0] Completed in 3967 milliseconds. 232 of 232 passed, 0 failed.
[Windows 8.1, Opera 20.0] Screenshot: https://s3.amazonaws.com/testautomation/77c2599aa28752c52ff4c26100a566b5981c8eac/js-screenshot-1396366653.png
[Tue Apr 01 2014 17:39:19 GMT+0200 (CEST)] [Runner alert] Tests timed out on: Windows 8, Chrome 32.0
[Tue Apr 01 2014 17:39:25 GMT+0200 (CEST)] [Runner alert] Tests timed out on: Windows 8.1, Firefox 27.0
[Tue Apr 01 2014 17:39:32 GMT+0200 (CEST)] [Runner alert] Tests timed out on: Windows 8.1, Opera 20.0
[Tue Apr 01 2014 17:39:42 GMT+0200 (CEST)] [Runner alert] Tests timed out on: OS X Mountain Lion, Safari 6.1
[Tue Apr 01 2014 17:39:46 GMT+0200 (CEST)] [Runner alert] Tests timed out on: OS X Mavericks, Safari 7.0
[Tue Apr 01 2014 17:39:54 GMT+0200 (CEST)] [Runner alert] Tests timed out on: Windows 7, Ie 9.0
[Tue Apr 01 2014 17:40:00 GMT+0200 (CEST)] [Runner alert] Tests timed out on: Windows XP, Ie 8.0
[Tue Apr 01 2014 17:40:07 GMT+0200 (CEST)] [Runner alert] Worker inactive for too long: Windows 8, Ie 10.0
[Tue Apr 01 2014 17:40:15 GMT+0200 (CEST)] [Runner alert] Worker inactive for too long: Windows 7, Ie 11.0
[Tue Apr 01 2014 17:40:23 GMT+0200 (CEST)] [Runner alert] Worker inactive for too long: Windows 8, Chrome 33.0
All tests done, failures: 10.
Exiting

For example, Chrome 32 completed, but also timed out. I can't tell why that would happen. Let me know what other information I could provide to help debug this.

[parisholley]

i also see this