You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Mac_ios hot_mode_dev_cycle_ios__benchmark is 2.00% flaky, Process exited with status = -1 (0xffffffff) lost connection #120808
The post-submit test builder Mac_ios hot_mode_dev_cycle_ios__benchmark had a flaky ratio 2.00% for the past (up to) 100 commits, which is above our 2.00% threshold.
The flake in 4015 is a host-side Dart VM GC crasher. I've only seen that once, and without a reliable repro, I don't think the VM team will be able to track that one down.
However, 3995 is a VM service address discovery timeout. It is interesting because the device logs don't capture the timeframe when the discovery timed out. Instead the device logs seem to begin only slightly before the run that follows the failing run. cc @jmagman.
Downgrading to P3 since this is only just over the threshold.
Hm, 4094 and 4171 lost connection to device, not sure what that's about? It ran on different devicelab bots.
[hot_mode_dev_cycle_ios__benchmark] [STDOUT] stdout: [+21099 ms] (lldb) warning: failed to set breakpoint site at 0x1b9c400f8 for breakpoint -4.1: error sending the breakpoint request
[hot_mode_dev_cycle_ios__benchmark] [STDOUT] stdout: [+5143 ms] Process 555 exited with status = -1 (0xffffffff) lost connection
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
zanderso commentedon Feb 15, 2023
The flake in 4015 is a host-side Dart VM GC crasher. I've only seen that once, and without a reliable repro, I don't think the VM team will be able to track that one down.
However, 3995 is a VM service address discovery timeout. It is interesting because the device logs don't capture the timeframe when the discovery timed out. Instead the device logs seem to begin only slightly before the run that follows the failing run. cc @jmagman.
Downgrading to P3 since this is only just over the threshold.
fluttergithubbot commentedon Feb 22, 2023
[prod pool] current flaky ratio for the past (up to) 100 commits is 3.06%. Flaky number: 3; total number: 98.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/4171
Commit: dad9eb2
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/4171
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/4160
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/4094
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac_ios%20hot_mode_dev_cycle_ios__benchmark
jmagman commentedon Feb 28, 2023
Hm, 4094 and 4171 lost connection to device, not sure what that's about? It ran on different devicelab bots.
4160 is VM service discovery timeout.
173 remaining items
fluttergithubbot commentedon Aug 30, 2023
[prod pool] flaky ratio for the past (up to) 100 commits between 2023-08-23 and 2023-08-29 is 4.26%. Flaky number: 4; total number: 94.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/6771
Commit: f489256
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/6771
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/6735
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/6732
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/6688
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac_ios%20hot_mode_dev_cycle_ios__benchmark
Retry connecting to device in CI after lost connection (#133769)
vashworth commentedon Sep 5, 2023
I pushed a workaround that should hopefully fix: #133769
Since we can't recreate it, though, we'll just have to wait to see if it stops flaking
fluttergithubbot commentedon Sep 6, 2023
[prod pool] flaky ratio for the past (up to) 100 commits between 2023-08-30 and 2023-09-03 is 1.03%. Flaky number: 1; total number: 97.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/6870
Commit: 1b1c8a1
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/6870
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac_ios%20hot_mode_dev_cycle_ios__benchmark
fluttergithubbot commentedon Sep 13, 2023
[prod pool] flaky ratio for the past (up to) 100 commits between 2023-09-07 and 2023-09-12 is 1.03%. Flaky number: 1; total number: 97.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/7043
Commit: 4a3ab68
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/7043
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac_ios%20hot_mode_dev_cycle_ios__benchmark
Don't uninstall before retrying to connect during app launch (#134542)
vashworth commentedon Sep 19, 2023
Updated the fix (#134542), so need to wait again to see if it stops flaking
fluttergithubbot commentedon Sep 20, 2023
[prod pool] flaky ratio for the past (up to) 100 commits between 2023-09-13 and 2023-09-19 is 2.22%. Flaky number: 2; total number: 90.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/7176
Commit: c2b1e48
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/7176
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20hot_mode_dev_cycle_ios__benchmark/7162
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac_ios%20hot_mode_dev_cycle_ios__benchmark
vashworth commentedon Sep 25, 2023
This has not flaked since workaround was added. I'm going to be cautiously optimistic and consider this fixed.
For future, if this error reoccurs, see the following comment for a breakdown of the situation:
#120808 (comment)
github-actions commentedon Oct 9, 2023
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.