Add --device-timeout flag to device-related commands#64834
Add --device-timeout flag to device-related commands#64834jmagman merged 2 commits intoflutter:masterfrom
Conversation
acac558 to
fe527f2
Compare
fe527f2 to
8d39e18
Compare
There was a problem hiding this comment.
@zanderso What do you think of this hard deprecation? I doubt this is commonly used. I didn't want to silently drop it. I could make it more complicated and print this warning, but then try to pass the deprecated timeout down into deviceDiscoveryTimeout.
There was a problem hiding this comment.
Plumbing it to deviceDiscovertyTimeout sounds like the right way to deprecate this. It can then be entirely removed after the stable branch cut.
There was a problem hiding this comment.
This has the side effect of repopulating the devices cache, with the timeout duration. We decided to do this in #51678 (comment) to avoid google3 breakages.
There was a problem hiding this comment.
Plumbing it to deviceDiscovertyTimeout sounds like the right way to deprecate this. It can then be entirely removed after the stable branch cut.
8d39e18 to
94691cc
Compare

Description
Deprecate
devicescommand--timeoutflag, replace with a command-level--device-timeoutflag. Also use influtter run,drive,attach,install,screenshot, andlogs.Related Issues
Another piece to #15072 to allow longer timeouts for networked devices.
This will allow devicelab tests to pass a longer timeout to
flutter drivefor tests targeting slower iOS devices.Tests
Added does/does not
refreshes device cache with a timeouttests.Checklist
///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change