Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(76)

Side by Side Diff: dart/tests/language/language.status

Issue 9111012: Detect crashes in frog/leg (when running on VM). (Closed) Base URL: ssh://aaricia.aar/home/ahe/Dart/all/dart.googlecode.com.git@master
Patch Set: Created 8 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 # Copyright (c) 2011, the Dart project authors. Please see the AUTHORS file 1 # Copyright (c) 2011, the Dart project authors. Please see the AUTHORS file
2 # for details. All rights reserved. Use of this source code is governed by a 2 # for details. All rights reserved. Use of this source code is governed by a
3 # BSD-style license that can be found in the LICENSE file. 3 # BSD-style license that can be found in the LICENSE file.
4 4
5 # This directory contains tests that are intended to show the 5 # This directory contains tests that are intended to show the
6 # current state of the language. 6 # current state of the language.
7 7
8 # In order to maintain maximum test coverage for all builds, 8 # In order to maintain maximum test coverage for all builds,
9 # please use the following procedure to mark a test 9 # please use the following procedure to mark a test
10 # failed on architectures other than the one you are working on. 10 # failed on architectures other than the one you are working on.
(...skipping 196 matching lines...) Expand 10 before | Expand all | Expand 10 after
207 # - should add a version of this with the --enable_type_checks flag 207 # - should add a version of this with the --enable_type_checks flag
208 # TypeVMTest - correctly skipped as this relies on detailed of TypeError 208 # TypeVMTest - correctly skipped as this relies on detailed of TypeError
209 # TypeDartcTest - should pass, need refactoring to get frog safe version 209 # TypeDartcTest - should pass, need refactoring to get frog safe version
210 210
211 BitOperationsTest: Fail # relies on big integers not available in JS 211 BitOperationsTest: Fail # relies on big integers not available in JS
212 CallThroughGetterTest: Fail 212 CallThroughGetterTest: Fail
213 CharEscapeTest: Fail 213 CharEscapeTest: Fail
214 ClassOverrideNegativeTest: Fail 214 ClassOverrideNegativeTest: Fail
215 ClosureSharedStateTest: Fail 215 ClosureSharedStateTest: Fail
216 ConstFactoryNegativeTest: Fail 216 ConstFactoryNegativeTest: Fail
217 ConstInit5NegativeTest: Pass # Should fail at compile-time, not at runtime
218 ConstInit7NegativeTest: Fail # Issue 1000 217 ConstInit7NegativeTest: Fail # Issue 1000
219 ConstObjectsAreImmutableTest: Fail 218 ConstObjectsAreImmutableTest: Fail
220 CTConstTest: Fail # Not checking for generic type in const expression.
221 DefaultFactoryLibraryTest: Fail # Issue 514 219 DefaultFactoryLibraryTest: Fail # Issue 514
222 DynamicTest: Fail 220 DynamicTest: Fail
223 ExampleConstructorTest: Fail 221 ExampleConstructorTest: Fail
224 Constructor2Test: Fail 222 Constructor2Test: Fail
225 Constructor3Test: Fail 223 Constructor3Test: Fail
226 Constructor5Test: Fail # Order of initializers. 224 Constructor5Test: Fail # Order of initializers.
227 Constructor6Test: Fail # Parse failure in initializers. 225 Constructor6Test: Fail # Parse failure in initializers.
228 ExecuteFinally6Test: Fail 226 ExecuteFinally6Test: Fail
229 ExpectTest: Fail 227 ExpectTest: Fail
230 #FauxverrideTest/01: Fail # see r607 (10/21) passes, but we should be issuing w arnings 228 #FauxverrideTest/01: Fail # see r607 (10/21) passes, but we should be issuing w arnings
(...skipping 107 matching lines...) Expand 10 before | Expand all | Expand 10 after
338 [ $component == frog || $component == frogsh ] 336 [ $component == frog || $component == frogsh ]
339 # these tests are inconsistent in frogium and frogsh-node, investigate 337 # these tests are inconsistent in frogium and frogsh-node, investigate
340 StaticField1RunNegativeTest: Pass 338 StaticField1RunNegativeTest: Pass
341 StaticField2RunNegativeTest: Pass 339 StaticField2RunNegativeTest: Pass
342 340
343 [ $component == frogium ] 341 [ $component == frogium ]
344 # these tests are inconsistent in frogium and frogsh-node, investigate 342 # these tests are inconsistent in frogium and frogsh-node, investigate
345 StaticField1RunNegativeTest: Pass # but error is not correct 343 StaticField1RunNegativeTest: Pass # but error is not correct
346 StaticField2RunNegativeTest: Pass # but error is not correct 344 StaticField2RunNegativeTest: Pass # but error is not correct
347 345
346
347 [ $component == frogsh || $component == frogium ]
ngeoffray 2012/01/05 12:09:19 Again, why are frogsh and frogium affected?
ahe 2012/01/05 12:14:44 They aren't. I have moved these tests from a frog+
348 ConstInit5NegativeTest: Pass # Should fail at compile-time, not at runtime
349 CTConstTest: Fail # Not checking for generic type in const expression.
350
351
352 [ $component == frog ]
353 ConstInit5NegativeTest: Crash
354 CTConstTest: Crash
355 Prefix19NegativeTest: Crash
356
357
348 [ $arch == x64 ] 358 [ $arch == x64 ]
349 *: Skip 359 *: Skip
350 360
351 [ $arch == simarm ] 361 [ $arch == simarm ]
352 *: Skip 362 *: Skip
353 363
354 [ $arch == arm ] 364 [ $arch == arm ]
355 *: Skip 365 *: Skip
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698