-
Todd Volkert authored
We're seeing occasional test timeouts trying to call `FlutterDriver.connect()`. Unfortunately, when the test is timed out at the test runner level, you don't get a meaningful test failure or stack trace of where the timeout occurrred. Your test harness also doesn't get to clean up, which can include things like saving the device logs to see what was going on in the device. Thus, this change adds timeouts in the places where we've most commonly observed hangs during tests.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
flutter | ||
flutter_driver | ||
flutter_localizations | ||
flutter_test | ||
flutter_tools | ||
fuchsia_remote_debug_protocol |