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
Linux_mokey large_image_changer_perf_android is 6.00% flaky #156945
The post-submit test builder Linux_mokey large_image_changer_perf_android had a flaky ratio 6.00% for the past (up to) 100 commits, which is above our 2.00% threshold.
Coming back to this just to dump info: this is clearly a race condition. The memory info (dumpsys meminfo) is not being run directly by the test. I believe it is devtools.
In both cases all tests pass; but some task in running / logging.
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
jtmcdole commentedon Oct 16, 2024
This looks like race conditions with stopping / uninstalling
jtmcdole commentedon Oct 16, 2024
@andrewkolos - is there another bug tracking this? Maybe this is a
driverrace condition?https://github.com/flutter/flutter/blob/main/dev/benchmarks/macrobenchmarks/test_driver/large_image_changer_test.dart
andrewkolos commentedon Oct 16, 2024
I am not personally aware of one
jtmcdole commentedon Oct 21, 2024
There is nothing I can do about this. This hasn't failed in the last 200 runs, so closing: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_mokey%20large_image_changer_perf_android?limit=200
jtmcdole commentedon Oct 21, 2024
Coming back to this just to dump info: this is clearly a race condition. The memory info (
dumpsys meminfo) is not being run directly by the test. I believe it is devtools.In both cases all tests pass; but some task in running / logging.
Good condition:
Race condition:
github-actions commentedon Nov 4, 2024
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.