Revise several already-committed CLs.

pkg/barback/test/package_graph/repetition_test.dart

Index: pkg/barback/test/package_graph/repetition_test.dart
diff --git a/pkg/barback/test/package_graph/repetition_test.dart b/pkg/barback/test/package_graph/repetition_test.dart
index cd9844049aaa42e72676ea80d4cbcf517d1bc47a..106a7074847106b087483779375ee5a296f5e4fd 100644
--- a/pkg/barback/test/package_graph/repetition_test.dart
+++ b/pkg/barback/test/package_graph/repetition_test.dart
@@ -9,6 +9,12 @@ import 'package:scheduled_test/scheduled_test.dart';
 
 import '../utils.dart';
 
+// This tests the behavior of barback under many operations happening in quick
+// succession. Since Barback is so asynchronous, it's easy for it to have subtle
+// dependencies on the commonly-used and -tested usage patterns. These tests
+// exist to stress-test less-common usage patterns in order root out additional

[Bob Nystrom, 2013/10/29 17:25:29]

"order root" -> "order to root".

[nweiz, 2013/10/29 19:27:26]

Done.

+// bugs.
+
 main() {
   initConfig();
 
@@ -45,7 +51,7 @@ main() {
     initGraph(["app|foo.txt"], {"app": [[rewrite]]});
     updateSources(["app|foo.txt"]);
 
-    for (var i = 0; i < 1; i++) {
+    for (var i = 0; i < 1000; i++) {
       updateTransformers("app", [[rewrite]]);
     }
 
@@ -58,7 +64,7 @@ main() {
     initGraph(["app|foo.txt"], {"app": [[rewrite]]});
     updateSources(["app|foo.txt"]);
 
-    for (var i = 0; i < 1; i++) {
+    for (var i = 0; i < 1000; i++) {
       updateTransformers("app", [[rewrite]]);
       updateTransformers("app", [[]]);
     }