-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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
Connect to VM timeout when doing integration tests #50898
Comments
I am also facing a similar issue, but it is when you try to pause the build and run in parallel, as mentioned in here -#41583 I am able to run the app on the devices and pause them as well, but unable to attach the driver to the URI this command |
Could be related #34196 |
@TahaTesser |
UPDATE: pixel_c repeatedly fail with this error. |
UPDATE: |
@tianhaoz95 |
@HerrNiklasRaab can you add the channel you were on? I tried stable. Maybe dev should be better? |
I was on stable to:
|
Interesting, this test failed 16 hours ago with |
oh actually nvm. it's a different issue |
I think that fixed it for me too! thanks! |
mark as resolved ;) |
actually after a few days I found that it only made the failure less frequent. It still happens. https://github.com/tianhaoz95/photochat/runs/478586086?check_suite_focus=true#step:6:2017 |
ping. any new findings on this? from the run I attached above, we can find that it happens only on Android. Is there a problem with Flutter + adb? |
Is there any progress? It's still flaky on all three channels. |
The same issue with real iOS device with 13.5.1 iPhone Xr [✓] Flutter (Channel unknown, v1.17.0, on Mac OS X 10.15.5 19F101, locale en-SK) [✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3) [✓] Xcode - develop for iOS and macOS (Xcode 11.5) [✓] Android Studio (version 4.0) [✓] Connected device (1 available) • No issues found! but for the some reason at start of integration test appears the following record: |
I'm getting the same issue as well any resolution so far? 00:00 +0: Todo App (setUpAll) VMServiceFlutterDriver: Connecting to Flutter application at http://127.0.0.1:8888/ flutter doctor -v
|
We began experiencing this after upgrading to 1.20.4. We did not see it previously on 1.17.5, but considering that this appears intermittently I'm not sure if that is valuable or not. This is really causing us some headaches in our build pipeline. We are specifically experiencing this on our android tests, not ios. |
I have the same issue occasionally. After I re-run it usually works ok. I am using Android 10.0 x86_x64 simulator without Google Play. Flutter doctor output:
|
Same issue here. It happens even in GitHub Actions, the CI environment. The output: https://github.com/fzyzcjy/flutter_rust_bridge/runs/3812009211 The workflow file: https://github.com/fzyzcjy/flutter_rust_bridge/actions/runs/1310850737/workflow |
We're also facing this problem. So very annoying. This makes integration testing have such a high flakiness ratio that it's a no-go. See also: |
Got the same problem on flutter 3.3.8 on emulator iPhone 14 pro max. |
Same issue here. Keeping us from being able to use integration tests since they can't be run consistently in CI/CD. |
This was mostly fixed in #113969 by the awesome @jakubfijalkowski. Should be available in the next stable Flutter release. |
I faced a similar issue on github runner when running the ios integration test by using the But if I specify the test file and the device |
same issue
|
Steps to Reproduce
flutter drive --target=test_driver/app.dart
.Expected results: the integration tests should start running in the emulator
Actual results: it keeps saying cannot connect to VM and finally timeout.
see this CI run: https://github.com/tianhaoz95/photochat/pull/17/checks?check_run_id=449361947#step:6:936
logs_157.zip
The text was updated successfully, but these errors were encountered: