More robust handling for errors in the runner.

[GoogleCodeExporter]

When something goes wrong in the runner, (bad json, dropped test) the 
runner hangs and causes issues through the system.

We need better handling during running.

Misko, please add the cyclical json structure case if you can recreate.

Original issue reported on code.google.com by corbinrs...@gmail.com on 14 Jan 2010 at 6:41

[GoogleCodeExporter]

Hi,

I've been having issues with significant load (i.e. a large number of tests 
submitted, albeit simple and serial tests) where test runs are cancelled are a 
certain point. There are two undesirable ways to solve this state:
1. refresh the browser
2. restart the server

It appears as if the communication from the server to the client breaks down 
and tests timeout after a certain point. The test is very simple. I'm 
essentially running 1000 copies of the same test. Server, browser and client 
runner all running on the same machine.

Could this be related to the issue described above?

Any help would be appreciated - when the server or client (it's difficult to 
tell) gets into this state it doesn't seem to be usable.

Original comment by Krish...@gmail.com on 11 Jul 2011 at 6:36

[GoogleCodeExporter]

I've experienced this issue as IE9 reports several JSON errors when launching 
the debugger before a test suite.

There also appears to be an issue with duplicate test naming, though no 
duplication exists.

IE9 often reports in the console:

SCRIPT1014: Invalid character 
runner.js, line 356 character 31684

IE will also throw  Method Access exception in some instances which are 
unrecoverable and cause the browser to hang, which ripples into the isFailure 
check inside the test  case's try/catch wrapper.  

Original comment by daCrazyC...@gmail.com on 10 Apr 2012 at 7:23