API 29 CI OOM fix #119
Closed
API 29 CI OOM fix #119
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Android test orchestrator runs each instrumentation test in isolation. This should isolate OOM crashes and one test should not crash the rest. Clear data after each test should also free memory. Also bumped up test dependencies' version.
This reverts commit bd1c572. API 29 is still failing with OOM.
* Reduced jvm maxHeap for ci gradle * Reduced test jvm maxHeap for tests Github actions has 7GB of RAM so reducing gradle RAM should leave more free for the emulator.
|
Is there a place where this is documented? I imagine there might be a stack overflow post? If so can you link it? Thanks. Btw i linked the issue here. |
|
Having thought about this -- can you separate the 3 different changes into separate PRs with CI runs? I'd love to understand exactly which one of these changes is fixing the issue! |
|
is this still needed? |
|
We are seeing some more out of memory errors now. @deepankarb do you think any of these fixes will be useful? |
|
I think they're worth a try. I'll run each option + current master as control 10 times to quantify if they reduce oom errors. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Attempting to fix
./gradlew connectedCheckOOM errors in Github Actions by reducing gradle and gradle test JVM max heap. This should make more RAM available for emulator.Gradle JVM heap reduced from 5 GB to 3 GB.
Gradle test JVM heap reduced from default to 256 MB.