Fix frogium build by disabling test for frog, frogsh AND frogium.

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 399 matching lines @@
 
 [ ($component == frogsh ||  $component == frog || $component == frogium) && $unchecked ]
 PrivateMemberTest/01: Fail # test seems bad - see issue #353
 PrivateMemberTest/02: Fail # test seems bad - see issue #353
 PrivateMemberTest/03: Fail # test seems bad - see issue #353
 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 == frogium ]
+IntrinsifiedMethodsTest: Fail # Issue 1470

[Jennifer Messerly, 2012/02/02 21:17:01]

I suspect this belongs up in the big block above:

  $component == frogsh ||  $component == frog || ($component == webdriver &&
($browser == chrome || $browser == ff || $browser == safari || $browser == ie))
|| $component == frogium

(unrelated note: I wonder if we can refactor "$component == webdriver &&
($browser == chrome || $browser == ff || $browser == safari || $browser == ie)"
into just "$component == webdriver"

[Ivan Posva, 2012/02/02 21:39:52]

It is nearly impossible for any of us to know what tests run under what
circumstance on what browser on which OS and what flags. So if you strongly feel
this should go somewhere else, please feel free to shuffle it around.

[Emily Fortuna, 2012/02/02 21:41:39]

+1 to  jmesserly's first comment. There is talk of also adding Opera, so I
wouldn't remove all the browser list just yet (sorry so verbose).

[Jennifer Messerly, 2012/02/02 21:50:04]

Totally understand! I get lost in all of our configurations for Dart too :-)

What caught my eye here is that this change added a new set of permutations
(frog || frogsh || frogium). That's why I was suggesting we move this test into
the other block, which is intended to mean "this test fails in frog, regardless
of configuration". Also, it means one less permutation to worry about :)

[Emily Fortuna, 2012/02/02 22:01:59]

Regardless of OS/browser combination, there are *four* components being tested: 
frog, frogsh, frogium, and webdriver. If you just specify webdriver as failing
for a particular test, you don't need to write out the browser combinations.

[Ivan Posva, 2012/02/02 23:02:41]

Could you please add comments to the file describing what the different
permutations mean? Thanks!

+
 [ $component == frog || $component == frogsh ]
 # these tests are inconsistent in frogium and frogsh-node, investigate
 StaticField1RunNegativeTest: Pass
 StaticField2RunNegativeTest: Pass
 SyntaxTest/28: Fail # Issue 1109
 SyntaxTest/29: Fail # Issue 1109
 SyntaxTest/31: Fail # Issue 1109
 SyntaxTest/32: Fail # Issue 1109
 SyntaxTest/33: Fail # Issue 1109
 StringEscape3NegativeTest: Fail # Issue 1352
 LiteralUnaryPlusTest/01: Fail # Issue 1400
-IntrinsifiedMethodsTest: Fail # Issue 1470
 
 [ $component == frogium ]
 # these tests are inconsistent in frogium and frogsh-node, investigate
 StaticField1RunNegativeTest: Pass # but error is not correct
 StaticField2RunNegativeTest: Pass # but error is not correct
 
-
 [ $arch == simarm ]
 *: Skip
 
 [ $arch == arm ]
 *: Skip