Make sure all isolates start during flutter driver tests.#61841
Make sure all isolates start during flutter driver tests.#61841fluttergithubbot merged 4 commits intoflutter:masterfrom
Conversation
|
@speaking-in-code Can you rebase this to the latest master to fix the analyzer problems? @dnfield Would you be up for reviewing this one since you're looking at e2e testing? |
|
I suspect you've tried to do a rebase that has gotten git a bit confused. Can you either open a new PR with just your changes, or fix up the history on this one? |
|
Fixed this PR, I think. |
There was a problem hiding this comment.
nit: prefer not shadowing parameter names in the enclosing class, which can get confusing. I don't have a great idea for a name here.
This does make me wonder if there are other cases we should be explicitly passing the isolate reference around though.
There was a problem hiding this comment.
Is there a reason we're not just setting the outter isoalte to isolateRef.load() here?
Should we be asserting isolate == isolateRef.load() somehow?
There was a problem hiding this comment.
Ahh I see, this could be other isolates the application uses that also started paused, right?
There was a problem hiding this comment.
Analyzer wants a type annotation on this array.
|
It looks like the checks are failing here due to a version solving error. Can you try to update your branch with the latest on master? |
So upstream linux is actually broken with this version solving problem: #62146. That will have to be fixed first, then this PR rebased to make CI green. |
|
Looks like this is ready to go except for the flutter-build check. Anything I can do to help resolve that? |
|
Added a label that will land this when those issues get resolved |
…utter#61841)" (flutter#62239) This reverts commit 5fa5701.
…utter#61841)" (flutter#62239) This reverts commit 5fa5701.

Description
Fixes #24703.
Fixes #30641
Fixes #30641
Flutter driver has problems when flutter apps use more than a single isolate. The other isolates don't start, so apps malfunction. This PR fixes the problem by listening for new isolates to become runnable, and automatically starting them.
Related Issues
#24703
Tests
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change
Did any tests fail when you ran them? Please read [Handling breaking changes].