remove node.js dependency by running the frog compiler in

tests/language/language.status

Index: tests/language/language.status
diff --git a/tests/language/language.status b/tests/language/language.status
index 14c4f6486e29cb7ed6c62753b88630b55dba6b30..0c07eb8ed9e8518b788499ba27f6f2efecb591ce 100644
--- a/tests/language/language.status
+++ b/tests/language/language.status
@@ -15,6 +15,16 @@
 # 2) File a bug on each architecture for the failure due to the language change.
 # 3) Update the language/src directory with the updated test.
 
+# TODO(mattsh) Once we move to the leg code generator, the javascript generated
+# by frog won't depend on whether frog is running on the dart vm or v8.  (The
+# leg compiler is designed to produce identical output no matter where it
+# is running.)  At that point we can make all the tests verify that the
+# generated javascript is identical between frogsh and frogium, and then only
+# need run the js once in the browser.  For now, just disable language
+# tests of frogsh to save time.
+[ $component == frogsh ]
+*: Skip
+
 [ $component == vm || $component == dartium ]
 GCTest: Fail # Issue 1487
 ImpliedInterfaceTest: Fail # Bug 5349944
@@ -196,11 +206,6 @@ RichardsTest: Fail
 StringEscape1NegativeTest: Skip
 GCTest: Skip # Issue 1487
 
-
-[ $component == frogsh ]
-IntrinsifiedMethodsTest: Fail # Issue 1470
-ArithmeticTest: Fail # Issue 1470
-
 # 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.
@@ -213,7 +218,7 @@ ArithmeticTest: Fail # Issue 1470
 # (Chrome, IE, Firefox, Safari, etc). If a test is only failing on a particular
 # browser, you can be more specific about the failure by using $browser:
 # [ $component == webdriver && $browser == chrome ] for example.
-[ $component == frog || $component == frogsh || $component == frogium || $component == webdriver]
+[ $component == frog || $component == frogium || $component == frogsh|| $component == webdriver]
 ExceptionTest: Fail # Issue 1785
 Factory3Test: Fail # Issue 417
 Factory2NegativeTest: Fail
@@ -222,7 +227,7 @@ DisablePrivacyTest: Skip  # Issue 1882: Needs --disable_privacy support.
 DoubleToStringAsExponentialTest: Fail # fails due to -0.0.
 # Once the -0.0 in DoubleToStringAsFixedTest is fixed it will probably need to
 # be moved to a
-# [ $component == frog || $component == frogium || $component == webdriver ]
+# [ $component == frog || $component == frogium || $component == frogsh || $component == webdriver ]
 # section.
 DoubleToStringAsFixedTest: Fail # fails due to -0.0 and due to rounding in constant propagation.
 DoubleToStringAsPrecisionTest: Fail # fails due to -0.0.
@@ -369,6 +374,9 @@ NamedParameters4Test: Fail
 
 StringEscape4NegativeTest: Fail # Issue 1352
 
+[ $component == frogium || $component == frogsh || $component == webdriver || $component == dartium ]
+ResourceTest: Fail  # browser tests are #sourcing the test, causing an error that directives cannot be used in #sourced files, see issue 1807
+
 [ $component == webdriver && $browser == chrome ]
 StringEscape1NegativeTest: Skip
 
@@ -423,7 +431,7 @@ PrivateMemberTest/04: Fail # test seems bad - see issue #353
 [ ($component == frogsh ||  $component == frog || $component == frogium) && $checked ]
 PrivateMemberTest/none: Fail # test seems bad - see issue #353
 
-[ $component == frog || $component == frogsh ]
+[ $component == frog ]
 # these tests are inconsistent in frogium and frogsh-node, investigate
 StaticField1RunNegativeTest: Pass
 StaticField2RunNegativeTest: Pass
@@ -435,7 +443,7 @@ SyntaxTest/33: Fail # Issue 1109
 StringEscape3NegativeTest: Fail # Issue 1352
 LiteralUnaryPlusTest/01: Fail # Issue 1400
 
-[ $component == frogium ]
+[ $component == frogium || $component == frogsh ]
 # these tests are inconsistent in frogium and frogsh-node, investigate
 StaticField1RunNegativeTest: Pass # but error is not correct
 StaticField2RunNegativeTest: Pass # but error is not correct