Quick fix for running release VM on frogium tests. (until we get the bots renamed)

tests/language/language.status

 # Copyright (c) 2012, 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.
 
 # This directory contains tests that are intended to show the
 # current state of the language.
 
 # In order to maintain maximum test coverage for all builds,
 # please use the following procedure to mark a test
 # failed on architectures other than the one you are working on.
@@ skipping 273 matching lines @@
 *FrogNegativeTest: Skip
 
 
 [ $component == dartium ]
 # TODO: These need to be retriaged.
 RichardsTest: Fail
 TypedMessageTest: Fail # Bug 5246195
 StringEscape1NegativeTest: Skip
 
 
-[ $component == frogsh || $component == webdriver || $component == frogium ]
+[ $component == frogsh || $component == frogium ]

[Emily Fortuna, 2012/02/08 02:19:32]

Now that we're running webdriver tests under frog, these pass.

 IntrinsifiedMethodsTest: Fail # Issue 1470
 ArithmeticTest: Fail # Issue 1470
 
 [ $component == frog ]
 ToStringAsFixedTest: Fail # fails due to rounding in constant propagation
 
 # This set of four test components (frog, frogsh, frogium, and webdriver) all
 # consume frog output, so if frog is generating the incorrect code, chances are
 # it will fail on all of these components.
 #
@@ skipping 237 matching lines @@
 
 [ $component == frog && $mode == debug ]
 ConstructorRedirect1NegativeTest: Skip # Undiagnosed infinite loop.
 ConstructorRedirect2NegativeTest: Skip # Undiagnosed infinite loop.
 
 [ $arch == simarm ]
 *: Skip
 
 [ $arch == arm ]
 *: Skip