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

Jump to bottom

Tests: Using undeclared identifier in static context is now warning #7337

Open
scheglov opened this issue Dec 12, 2012 · 10 comments
Open

Tests: Using undeclared identifier in static context is now warning #7337

scheglov opened this issue Dec 12, 2012 · 10 comments
Labels
area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@scheglov
Copy link
Contributor

Following tests expect that using prefixed undeclared identifier in static context in error.

prefix12_negative_test: Fail
prefix2_negative_test: Fail

See also http://code.google.com/p/dart/issues/detail?id=6836
@anders-sandholm
Copy link
Contributor

Removed this from the M3 milestone.
Added this to the M4 milestone.

@larsbak
Copy link

larsbak commented May 28, 2013

Removed this from the M4 milestone.
Added this to the M5 milestone.

@kasperl
Copy link

kasperl commented Jun 4, 2014

Removed this from the M5 milestone.
Added this to the 1.6 milestone.

@kasperl
Copy link

kasperl commented Jul 10, 2014

Removed this from the 1.6 milestone.
Added Oldschool-Milestone-1.6 label.

@kasperl
Copy link

kasperl commented Aug 4, 2014

Removed Oldschool-Milestone-1.6 label.

@scheglov scheglov added Type-Defect area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). labels Aug 4, 2014
@srawlins
Copy link
Member

Why isn't this labeled with an area-dart2js or an area-analyzer tag?

@scheglov
Copy link
Contributor Author

Because it is area-test - shared tests for all Dart tools.

@srawlins
Copy link
Member

I see. So there is no dart2js bug or analyzer bug? Just a bug in the test files.

@scheglov
Copy link
Contributor Author

Yes, this is a bug in the test files.
It is not an error in analyzer.

@kevmoo kevmoo added P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed triaged labels Feb 29, 2016
@matanlurey matanlurey added closed-obsolete Closed as the reported issue is no longer relevant and removed closed-obsolete Closed as the reported issue is no longer relevant labels Jun 21, 2018
@srawlins
Copy link
Member

All of these tests are still marked as Fail. Check with git grep 'prefix12_negative_test' and git grep 'prefix2_negative_test'. Both are marked as Fail in pkg/front_end/test/fasta/parser/parser.status and pkg/front_end/test/fasta/scanner/scanner.status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@kevmoo @srawlins @matanlurey @scheglov @kasperl @anders-sandholm @larsbak