Mac tool_integration_tests_4_4 is 2.22% flaky

[fluttergithubbot]

The post-submit test builder Mac tool_integration_tests_4_4 had a flaky ratio 2.22% for the past (up to) 100 commits, which is above our 2.00% threshold.

One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20tool_integration_tests_4_4/10880
Commit: 40bb615

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20tool_integration_tests_4_4/10880
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac%20tool_integration_tests_4_4/10796

Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac%20tool_integration_tests_4_4

Please follow https://github.com/flutter/flutter/wiki/Reducing-Test-Flakiness#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).

[zanderso]

Routing to tools team.

[christopherfujino]

10880 is a gradle error:

FAILURE: Build failed with an exception.

* Where:
Script '/Volumes/Work/s/w/ir/x/w/flutter/packages/flutter_tools/gradle/src/main/groovy/flutter.groovy' line: 276

* What went wrong:
A problem occurred evaluating script.
> Failed to apply plugin class 'FlutterPlugin'.
   > Could not open cache directory 41rl0ui7kgmsyfwn97o2jypl6 (/Volumes/Work/s/w/ir/cache/gradle/caches/6.7/gradle-kotlin-dsl/41rl0ui7kgmsyfwn97o2jypl6).
      > Failed to create Jar file /Volumes/Work/s/w/ir/cache/gradle/caches/6.7/generated-gradle-jars/gradle-api-6.7.jar.

And

10796 is actually #121705

[christopherfujino]

Regarding 10880, per gradle/gradle#9642 it looks like this is an upstream flake that was never resolved. Action item here is probably to add "Could not open cache directory" to https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/android/gradle_errors.dart#L68

[christopherfujino]

Closing this one as the gradle error was worked around in #129222 and the Dart GC segfault is being tracked in #121705

[github-actions]

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.