Fix date_time_test to not assume a particular slowness of running code.

tests/corelib/date_time_test.dart

Index: tests/corelib/date_time_test.dart
diff --git a/tests/corelib/date_time_test.dart b/tests/corelib/date_time_test.dart
index 62c8ab880b7445fc75edf84a0f3e3ada472d5013..93d8fd796da322234f5b4bdc921289d6a665656e 100644
--- a/tests/corelib/date_time_test.dart
+++ b/tests/corelib/date_time_test.dart
@@ -13,14 +13,12 @@ const int _MAX_MILLISECONDS = 8640000000000000;
 void testNow() {
   var t1 = new DateTime.now();
   bool timeMovedForward = false;
-  for (int i = 0; i < 1000000; i++) {
+  while (true) {
     var t2 = new DateTime.now();

[ricow1, 2014/12/03 06:55:46]

I would add a count, and print to stdout for every 1,000,000 iterations, that
way we actually know that we are waiting here if the test should time out,
something like:
print("Still waiting for time to move forward: t1 was
${t1.millisecondsSinceEpoch}, t2 was {t2.millisecondsSinceEpoch}, did $count
calls to DateTime.now()")

[Lasse Reichstein Nielsen, 2014/12/03 07:14:47]

Done.

     if (t1.millisecondsSinceEpoch < t2.millisecondsSinceEpoch) {
-      timeMovedForward = true;
       break;
     }
   }
-  Expect.equals(true, timeMovedForward);
   Expect.isFalse(t1.isUtc);
 }