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
flutter build "apk" succeeds without libraries from native_assets_without_cbuild_assemble_test.dart is slow and flaky #158560
The post-submit test builder Linux tool_integration_tests_6_6 had a flaky ratio 6.25% for the past (up to) 100 commits, which is above our 2.00% threshold.
There's only been 36 runs on this configuration, so the reported flaky rate may be slightly higher than the actual rate.
It looks like flutter build "apk" succeeds without libraries in native_assets_without_cbuild_assemble_test.dart is failing due to a timeout and an unexpected exit code from Gradle.
I'm assigning this to @matanlurey (who recently rewrote this test) and @dcharkes (who owns native asset functionality) to investigate further.
changed the title [-]Linux tool_integration_tests_6_6 is 6.25% flaky[/-][+]`flutter build "apk" succeeds without libraries` from `native_assets_without_cbuild_assemble_test.dart` is slow and flaky[/+]on Nov 13, 2024
I think a no-brainer move is to just disable the apk variant of the tests for now, the actual functionality being tested by this is specific for macOS, and while it would be great to have more coverage I wouldn't even know where to start in terms of debugging why this specific test configuration times out (maybe hidden Java heap issues?)
I also wonder if this is similar to @andrewkolos' other investigations (i.e. #157847) where it appears that flutter build apk can just take wildly different amounts of time or #152604 where OOMs are the cause.
Interestingly enough android_plugin_example_app_build_test.dart which otherwise is doing something very similar, does not appear to have this problem. The only difference I can see is the AGP version being used?
As of #158757 I am going to watch this build for the rest of the day - if it is extra bad I can disable and create a bringup shard so it doesn't disrupt the rest of the team.
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
bkonyi commentedon Nov 13, 2024
There's only been 36 runs on this configuration, so the reported flaky rate may be slightly higher than the actual rate.
It looks like
flutter build "apk" succeeds without librariesinnative_assets_without_cbuild_assemble_test.dartis failing due to a timeout and an unexpected exit code from Gradle.I'm assigning this to @matanlurey (who recently rewrote this test) and @dcharkes (who owns native asset functionality) to investigate further.
[-]Linux tool_integration_tests_6_6 is 6.25% flaky[/-][+]`flutter build "apk" succeeds without libraries` from `native_assets_without_cbuild_assemble_test.dart` is slow and flaky[/+]matanlurey commentedon Nov 13, 2024
I think a no-brainer move is to just disable the
apkvariant of the tests for now, the actual functionality being tested by this is specific for macOS, and while it would be great to have more coverage I wouldn't even know where to start in terms of debugging why this specific test configuration times out (maybe hidden Java heap issues?)matanlurey commentedon Nov 13, 2024
I also wonder if this is similar to @andrewkolos' other investigations (i.e. #157847) where it appears that
flutter build apkcan just take wildly different amounts of time or #152604 where OOMs are the cause.matanlurey commentedon Nov 13, 2024
Interestingly enough android_plugin_example_app_build_test.dart which otherwise is doing something very similar, does not appear to have this problem. The only difference I can see is the AGP version being used?
Stream the output of `flutter build` for debugging. (#158757)
matanlurey commentedon Nov 13, 2024
As of #158757 I am going to watch this build for the rest of the day - if it is extra bad I can disable and create a bringup shard so it doesn't disrupt the rest of the team.
matanlurey commentedon Nov 13, 2024
Failed again, here is the output:
6 remaining items
matanlurey commentedon Nov 15, 2024
I am adding more skips, and also trying to reproduce the failures on a bringup shard.
Try running historically flaky tests first to make `flutter build apk…
Further skip `native_assets_test`(s) that runs `flutter build apk`. (#…
Reverts "Try running historically flaky tests first to make `flutter …
Switch `flutter_build_apk_health_tests` to use a subset of current te…
dcharkes commentedon Nov 18, 2024
Thanks for picking this up @matanlurey while I was out! 🙏
Since you're on it, and it's not native assets specific, I'll go ahead and unassign myself. Please let me know if you need me. ☎️
fluttergithubbot commentedon Nov 20, 2024
[prod pool] flaky ratio for the past (up to) 100 commits between 2024-11-12 and 2024-11-19 is 2.00%. Flaky number: 2; total number: 100.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20tool_integration_tests_6_6/42
Commit: 9a50759
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20tool_integration_tests_6_6/42
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20tool_integration_tests_6_6/37
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux%20tool_integration_tests_6_6
Un-skip tests that use `flutter build apk`. (#159231)
github-actions commentedon Dec 5, 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.