-
Notifications
You must be signed in to change notification settings - Fork 29.1k
[web] define $flutterDriverResult variable early in driver test initalization #107337
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
Conversation
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!). If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
Linked #107545 as well, that looks like a dup of the original issue this was fixing (in a different shard) |
7bb372f
to
f0a14c4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only little nitpicks with the js-interop style, and maybe adding a watchdog to the self-check bits of the sendCommand
method.
Define
$flutterDriverResult
during driver VM service extension initialization, so that by the timeweb_driver.dart
is checking for its value it is guaranteed to be available. Otherwise, there's a race between the time the variable is checked, and the time the first driver command initializes it.Fixes #102660
Fixes #107545