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.

Sign up for GitHub

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

Front-end fails package get tests due to hard-coded analyzer path #27655

Open
whesse opened this issue Oct 24, 2016 · 1 comment
Open

Front-end fails package get tests due to hard-coded analyzer path #27655

whesse opened this issue Oct 24, 2016 · 1 comment
Labels
area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test).

Comments

@whesse
Copy link
Contributor

whesse commented Oct 24, 2016

The front-end package fails the pkgbuild tests due to a hardcoded {path: } in the pubspec for kernel.

When this is replaced with a version, and the lookup happens through .packages, please remove the status line in [sdk]/pkg/pkgbuild.status.

Please set the labels for this bug - I couldn't find a "front-end" label.

@stereotype441 @sigmundch
@whesse whesse added the area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). label Oct 24, 2016
whesse added a commit that referenced this issue Oct 24, 2016
@whesse
Update pkgbuild status for analyzer and front-end.
057b9ce 
BUG=#27655
BUG=#27654
R=sortie@google.com

Review URL: https://codereview.chromium.org/2440423002 .
@whesse whesse mentioned this issue Nov 30, 2016
Open
@stereotype441 stereotype441 removed their assignment Apr 13, 2023
@stereotype441
Copy link
Member

Unassigning myself because I’m not actively working on this issue right now.

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).
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stereotype441 @whesse