Skip to content

Problematic test: checking the rootLibrary #12188

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
Closed
rmacnak-google opened this issue Aug 1, 2013 · 3 comments
Closed

Problematic test: checking the rootLibrary #12188

rmacnak-google opened this issue Aug 1, 2013 · 3 comments
Labels
area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@rmacnak-google
Copy link
Contributor

mirrors/local_isolate_test

The rootLibrary depends on how program started. On Dartium, test.local_isolate_test is not the root library because the program starts from another test harness.
@peter-ahe-google
Copy link
Contributor

The problem is that we're still wrapping tests in dartium, see issue #2264.

Removed the owner.

@rmacnak-google rmacnak-google added Type-Defect area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). labels Aug 6, 2013
@kevmoo kevmoo added type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed priority-unassigned labels Feb 29, 2016
@bkonyi
Copy link
Contributor

bkonyi commented Jun 18, 2018

Is this a Dartium only issue?

@rmacnak-google
Copy link
Contributor Author

This was a Dartium test harness issue.

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). type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kevmoo @peter-ahe-google @rmacnak-google @bkonyi