Windows tool integration tests are flaky: "Java heap space" #157640
Description
One example failure:
20:00 +25 -1: test/integration.shard/isolated/native_assets_test.dart: flutter build apk succeeds without libraries [E]
Exception: flutter build failed: 1
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:compressDebugAssets'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.CompressAssetsWorkAction
> Java heap space
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org/.
BUILD FAILED in 42s
Gradle task assembleDebug failed with exit code 1
Running Gradle task 'assembleDebug'...
Running Gradle task 'assembleDebug'... 43.9s
test\integration.shard\isolated\native_assets_test.dart 240:11 main.<fn>.<fn>
===== asynchronous gap ===========================
test\integration.shard\isolated\native_assets_test.dart 803:5 inTempDir
===== asynchronous gap ===========================
test\integration.shard\isolated\native_assets_test.dart 226:7 main.<fn>Looking at the try-bots, these don't seem particularly healthy:
