-
Notifications
You must be signed in to change notification settings - Fork 28.6k
Flake in DartIsolateTest.ValidLoadingUnitSucceeds #72312
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
Comments
This test looks very suspicious. It looks like there are potentially two |
This is my test, I'll take a look. |
Is this blocking anything? If it is, I can temporarily disable it, since I traced the problem somewhere rather opaque within dart. Since this (should be) the first usage of this dart feature, it may take a bit of time to properly resolve. |
Getting this unit test passing seems like it would be a prerequisite for declaring success on deferred-loading/split AOT? |
Yeah, though after chatting with Ryan about the problem, it seems it is most likely to be a problem with the testing infra rather than the split aot feature itself. |
Sure. We should do whatever is the necessary work to write a non-flaky test of the thing you're trying to test. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
From engine flake triage: @GaryQian Did you get a chance to look into this further? The test is still disabled. |
Not yet, I can look into it next. |
@GaryQian any update? |
Due to limitations in dart in a test env, I plan on testing this with a full integration test on an AVD instead as a unit test. My other line of work getting AVDs running in pre and postsubmit luci will make this test possible |
PR for integration tests to properly test this: #88030 |
@GaryQian Can we close this issue? |
From flaky issue triage: @GaryQian Did you delete the flaky test? Can we close this? |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Uh oh!
There was an error while loading. Please reload this page.
Seeing this flake:
The text was updated successfully, but these errors were encountered: