Remove Dartium support from test.dart.

tools/testing/dart/command_output.dart

 // Copyright (c) 2017, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
 import 'dart:convert';
 // We need to use the 'io' prefix here, otherwise io.exitCode will shadow
 // CommandOutput.exitCode in subclasses of CommandOutput.
 import 'dart:io' as io;
 
 import 'browser_controller.dart';
@@ skipping 87 matching lines @@
     if (outcome == Expectation.ignore) return outcome;
     if (outcome.canBeOutcomeOf(Expectation.fail)) {
       return Expectation.pass;
     }
     return Expectation.fail;
   }
 }
 
 class ContentShellCommandOutput extends CommandOutput {
   // Although tests are reported as passing, content shell sometimes exits with
-  // a nonzero exitcode which makes our dartium builders extremely falky.
+  // a nonzero exitcode which makes our builders extremely flaky.
   // See: http://dartbug.com/15139.
   // TODO(rnystrom): Is this still needed? The underlying bug is closed.
   static const _whitelistedContentShellExitCode = -1073740022;
 
   static bool _failedBecauseOfFlakyInfrastructure(
       Command command, bool timedOut, List<int> stderrBytes) {
     // If the browser test failed, it may have been because content shell
     // and the virtual framebuffer X server didn't hook up, or it crashed with
     // a core dump. Sometimes content shell crashes after it has set the stdout
     // to PASS, so we have to do this check first.
@@ skipping 711 matching lines @@
     // complete successfully, it's outcome is Expectation.FAIL.
     // TODO: maybe we should introduce a AsyncIncomplete marker or so
     if (outcome == Expectation.pass) {
       if (_isAsyncTest(testOutput) && !_isAsyncTestSuccessful(testOutput)) {
         return Expectation.fail;
       }
     }
     return outcome;
   }
 }