Skip to content

co19_2/ new failing tests #805

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

Closed
scheglov opened this issue Jul 9, 2020 · 6 comments
Closed

co19_2/ new failing tests #805

scheglov opened this issue Jul 9, 2020 · 6 comments
Assignees

Comments

@scheglov
Copy link

scheglov commented Jul 9, 2020

With https://dart-review.googlesource.com/c/sdk/+/153742, new co19_2 tests are failing, because analyzer makes some diagnostics warnings instead of errors. The language specification says that they are warnings.

So, following tests are fixed:

co19/Language/Classes/Instance_Methods/Operators/return_type_t01
co19/Language/Classes/Setters/return_type_not_void_t01
co19/Language/Classes/Setters/syntax_t04
co19/Language/Classes/Setters/syntax_t05
co19/Language/Libraries_and_Scripts/Imports/library_name_t01

And the following tests are broken:

co19_2/Language/Classes/Instance_Methods/Operators/return_type_t01
co19_2/Language/Classes/Setters/return_type_not_void_t01
co19_2/Language/Classes/Setters/same_name_getter_different_type_t01
co19_2/Language/Classes/Setters/syntax_t04
co19_2/Language/Classes/Setters/syntax_t05
co19_2/Language/Libraries_and_Scripts/Imports/library_name_t01

I don't know if we want to spend time updating co19_2/ tests, but want to document why I'm accepting breakages of these tests on bots. @eernstg

@sgrekhov
Copy link
Contributor

sgrekhov commented Aug 5, 2020

@scheglov CL, mentioned in this issue was abandonded. Is this issue still actual then?

@eernstg
Copy link
Member

eernstg commented Aug 5, 2020

Looking at the co19 repo (branch pre-nnbd) I don't see any missing updates in the co19_2 tests:

  • co19_2/Language/Classes/Instance_Methods/Operators/return_type_t01 is an error, expects an error: OK.
  • co19_2/Language/Classes/Setters/return_type_not_void_t01 is an error, expects an error: OK.
  • co19_2/Language/Classes/Setters/same_name_getter_different_type_t01 is an error, expects an error: OK.
  • co19_2/Language/Classes/Setters/syntax_t04 is an error, expects an error: OK (don't know why it's called 'syntax').
  • co19_2/Language/Classes/Setters/syntax_t05 is an error, expects an error: OK (don't know why it's called 'syntax').
  • co19_2/Language/Libraries_and_Scripts/Imports/library_name_t01 no errors, expects no errors: OK.

But the co19 tests (branch master) except the library name test still expect warnings, so they should be updated to expect errors:

  • co19/Language/Classes/Instance_Methods/Operators/return_type_t01 is error, expects warning: Update.
  • co19/Language/Classes/Setters/return_type_not_void_t01 is error, expects warning: Update.
  • co19/Language/Classes/Setters/syntax_t04 is error, expects warning: Update.
  • co19/Language/Classes/Setters/syntax_t05 is error, expects warning: Update.
  • co19/Language/Libraries_and_Scripts/Imports/library_name_t01 no errors, expects no errors: OK.

So, presumably, the co19 tests have already been updated to expect warnings, but they should now be changed back because we changed the spec to require errors (which means that the analyzer already did the right thing).

@scheglov
Copy link
Author

scheglov commented Aug 5, 2020

I think we also need to change these tests from warnings to compile-time errors:

co19/Language/Classes/Setters/same_name_getter_different_type_t01
co19/Language/Classes/Setters/same_name_getter_different_type_t02

@scheglov scheglov reopened this Aug 5, 2020
@sgrekhov
Copy link
Contributor

sgrekhov commented Aug 6, 2020

@eernstg after the change tests
co19/Language/Classes/Instance_Methods/Operators/return_type_t01
co19/Language/Classes/Setters/return_type_not_void_t01
co19/Language/Classes/Setters/syntax_t04
co19/Language/Classes/Setters/syntax_t05
started failing on CFE with MissedCompileError. Do we have a corresponding issue for CFE? I was unable to find it.

@eernstg
Copy link
Member

eernstg commented Aug 7, 2020

Cf. dart-lang/language#1012 (comment), I think it's #42701, #42702.

@sgrekhov
Copy link
Contributor

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants