Rewrite HTML5 workers ui_tests to browser_tests. Compared to ui_tests, browser_tests are faster, le…

chrome/test/data/workers/terminate_queued_workers.html

Index: chrome/test/data/workers/terminate_queued_workers.html
===================================================================
--- chrome/test/data/workers/terminate_queued_workers.html	(revision 129415)
+++ chrome/test/data/workers/terminate_queued_workers.html	(working copy)
@@ -8,7 +8,7 @@
 var workers = [];
 function startAndTerminateWorkers() {
   var terminateCount = 0;
-  for (var i = 0 ; i < 200 ; i++) {
+  for (var i = 0 ; i < 16 ; i++) {
     var w = new Worker("worker_common.js");
     workers.push(w);
     w.postMessage("ping");
@@ -17,11 +17,6 @@
       if (terminateCount == 16) {
         shutdownWorkers();
       }
-      if (terminateCount > 16) {
-        // Should not get more than 16 messages back unless we raise the worker
-        // limit.

[Andrew T Wilson (Slow), 2012/03/28 22:44:09]

Why did we get rid of this check? Was it race-y?

[jam, 2012/03/28 23:01:27]

now we can run more than 16 workers with isolates

[Andrew T Wilson (Slow), 2012/03/28 23:49:27]

Note that now this test doesn't actually do much useful if we can't cause queued
workers. Doesn't hurt to keep it around, but it doesn't actually do what it
claims (queue up workers, then terminate them before they can get started).

[jam, 2012/03/29 01:03:41]

good point. I tried to switch it to a SharedWorker but didn't see a way to
terminate it. I tried removing a reference to it but then I think this would
just be racy on when it dies, so it's not that useful (correct me if I'm wrong).
deleted the test

-        onFailure();
-      }
     }
   }
 }