Fix an issue where test timeouts would cause no more tests to execute.

pkg/unittest/lib/unittest.dart

Index: pkg/unittest/lib/unittest.dart
===================================================================
--- pkg/unittest/lib/unittest.dart	(revision 28320)
+++ pkg/unittest/lib/unittest.dart	(working copy)
@@ -750,6 +750,7 @@
       try {
         timer = new Timer(timeout, () {
           testCase.error("Test timed out after ${timeout.inSeconds} seconds.");
+          _nextTestCase();

[ahe, 2013/10/11 12:59:41]

This makes sense. Do you need the BREATH_INTERVAL as well?

[devoncarew, 2013/10/11 16:16:47]

Looks like. A series of test timeouts could prevent DOM events from being
processed for a while. I'll look at creating an _advanceTestCase() method,
calling it from here, and moving that Timer.run()/runAsync() logic from below
into that method.

         });
       } on UnsupportedError catch (e) {
         if (e.message != "Timer greater than 0.") rethrow;
@@ -858,13 +859,13 @@
 bool formatStacks = true;
 
 /**
- * A flag that controls whether we try to filter out irrelevant frames from 
+ * A flag that controls whether we try to filter out irrelevant frames from
  * the stack trace. Requires formatStacks to be set.
  */
 bool filterStacks = true;
 
 /**
- * Returns a Trace object from a StackTrace object or a String, or the 
+ * Returns a Trace object from a StackTrace object or a String, or the
  * unchanged input if formatStacks is false;
  */
 Trace _getTrace(stack) {