build(test): raise the unit test JVM heap to 4096m

[Lemkinator]

Summary

Robolectric NATIVE graphics, Roborazzi and several SDK sandboxes share one test fork. Together they outgrow Gradle's 512m default heap. The unit test fork now gets 4096m, matching the shared fleet build config.

Behavior changes

None: test build config only.

Verification

• testDebugUnitTest passes.

🤖 Generated with Claude Code

https://claude.ai/code/session_011T1VTy3Z9tJ2Z5NxtpMP8x

Set the maximum heap size to 4096m for unit-test JVM tasks in app/build.gradle.kts.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: e7aa1962-2a71-4e05-a36e-2bbe546c2308

📥 Commits

Reviewing files that changed from the base of the PR and between 7f26842 and 190d9d9.

📒 Files selected for processing (1)

• app/build.gradle.kts

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The app Gradle configuration now sets a maximum heap size of 4096m for unit-test JVM tasks.

Changes

Unit-test heap configuration

Layer / File(s)	Summary
Set unit-test heap size app/build.gradle.kts	Unit-test JVM tasks now have a maximum heap size of 4096m.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 190d9

The change raises the unit-test JVM’s heap ceiling without changing app runtime behavior. No concrete CI memory-budget failure is established, so no actionable merge-blocking risk remains.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: increasing the unit-test JVM heap to 4096m.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks the test-task heap,
And sets its bounds both broad and deep.
Four gigabytes now wait in store,
For unit tests that need some more.
The config rests; the carrots sleep.}

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Confidence Score: 5/5

[Low risk] Increases memory for unit test execution.

The PR appears safe to merge.

Summary

The PR raises the app unit-test JVM heap limit to 4096m for local unit tests and screenshot verification. It does not change application behavior.

_{Reviews (1) · Last reviewed commit: "build(test): raise the unit test JVM hea..."}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!