Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dart2dart test in checked mode has lots of errors. #13403

Closed
lrhn opened this issue Sep 18, 2013 · 0 comments
Closed

Dart2dart test in checked mode has lots of errors. #13403

lrhn opened this issue Sep 18, 2013 · 0 comments
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue

Comments

@lrhn
Copy link
Member

lrhn commented Sep 18, 2013

The following test results were considered failures when running tests as:
  tools/test.py --checked -cdart2dart

co19/Language/13_Statements/09_Switch_A05_t01: Pass
co19/Language/14_Libraries_and_Scripts/1_Imports_A03_t26: Pass
co19/Language/15_Types/1_Static_Types_A03_t01: Pass
co19/LibTest/async/EventTransformStream/contains_A01_t01: Pass
co19/LibTest/core/List/removeAt_A02_t01: Pass
co19/LibTest/core/Uri/encodeFull_A01_t02: Pass
language/assign_static_type_test/01: Fail
language/assign_static_type_test/02: Fail
language/assign_static_type_test/03: Fail
language/assign_static_type_test/04: Fail
language/assign_static_type_test/05: Fail
language/callable_test/00: Fail
language/callable_test/01: Fail
language/compile_time_constant_checked_test/01: Fail
language/compile_time_constant_checked_test/03: Fail
language/default_factory2_test/01: Fail
language/factory1_test/00: Fail
language/factory1_test/01: Fail
language/factory_implementation_test/00: Fail
language/factory_redirection_test/08: Fail
language/factory_redirection_test/09: Pass
language/factory_redirection_test/10: Fail
language/factory_redirection_test/11: Fail
language/factory_redirection_test/12: Fail
language/factory_redirection_test/13: Fail
language/factory_redirection_test/14: Pass
language/field_override_test/02: Fail
language/field_type_check2_test/01: Fail
language/field_type_check_test/01: Fail
language/getters_setters2_test/03: Fail
language/redirecting_factory_infinite_steps_test/01: Fail
language/redirecting_factory_malbounded_test/01: Fail
language/type_variable_bounds2_test/00: Fail
language/type_variable_bounds2_test/02: Fail
language/type_variable_bounds2_test/03: Fail
language/type_variable_bounds2_test/05: Fail
language/type_variable_bounds2_test/06: Fail
language/type_variable_bounds3_test/00: Fail
language/type_variable_bounds_test/01: Fail
language/type_variable_bounds_test/02: Fail
language/type_variable_bounds_test/04: Fail
language/type_variable_bounds_test/05: Fail

@sethladd sethladd added the closed-not-planned Closed as we don't intend to take action on the reported issue label Jul 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue
Projects
None yet
Development

No branches or pull requests

3 participants