Cleaning up unittest configurations

pkg/unittest/lib/vm_config.dart

Index: pkg/unittest/lib/vm_config.dart
diff --git a/pkg/unittest/lib/vm_config.dart b/pkg/unittest/lib/vm_config.dart
index 3a9efb831cffb35b5de5f91f91e2ff35769ecb00..0b23996fea54dcb8ba58f4da17f974d41129a598 100644
--- a/pkg/unittest/lib/vm_config.dart
+++ b/pkg/unittest/lib/vm_config.dart
@@ -10,19 +10,20 @@ library unittest_vm_config;
 import 'dart:io';
 import 'unittest.dart';
 
-class VmConfiguration extends Configuration {
-  void onDone(int passed, int failed, int errors, List<TestCase> results,
-      String uncaughtError) {
+class VMConfiguration extends Configuration {
+  void onDone(bool success) {
     try {
-      super.onDone(passed, failed, errors, results, uncaughtError);
-    } on Exception catch (ex) {
+      super.onDone(success);
+    } catch (ex) {
       // A non-zero exit code is used by the test infrastructure to detect
       // failure.
       exit(1);
     }
   }
+
+  void notifyController(String msg) {}
 }
 
-void useVmConfiguration() {

[Jennifer Messerly, 2013/01/10 03:01:18]

totally optional but: is it worth having an @deprecated forward for this method,
and remove after this build goes out?

(guessing a decent number of people are using unittest, so they might be calling
this method)

-  configure(new VmConfiguration());
+void useVMConfiguration() {
+  configure(new VMConfiguration());
 }