-
Notifications
You must be signed in to change notification settings - Fork 137
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
Test drive never starting because of failed connection to VMServiceFlutterDriver #272
Comments
The possible solution I mentioned above doesn't work. If the driver can't connect for the first time, then it can't connect for the 2nd, 3rd, and n-th time as well. That's why I reverted the PRs (see above). Another approach that we could try: look into replacing the default integration driver (in import 'package:integration_test/integration_test_driver.dart';
Future<void> main() => integrationDriver(); with something ours that would have retry semantics. See also: |
We've freed ourselves from |
This issue has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar problem, please file a new issue. Make sure to follow the template and provide all the information necessary to reproduce the issue. |
See this workflow run. Out of 6 jobs, 3 succeeded, 1 failed, and 2 timed out. This issue is about getting rid of those timeouts.
It looks that sometimes Flutter Driver can't connect to the service running on the Dart VM, and waits indefinitely.
This how logs from the "corrupt" state look like:
And this is how logs look like when everything is OK:
The solution I'd try out is to check for logs containing, for example
VMServiceFlutterDrive: VMServiceFlutterDriver: Unknown pause event type Event. Assuming application is ready.
and if it occurs, try to connect once again. We could also go the other way around and wait for the connection for a few seconds and then try to reconnect.The text was updated successfully, but these errors were encountered: