Files
amethyst/.github
Claude 08a2710039 ci: give the Android job room for a cold Gradle cache
test-and-build-android was killed at its 60-minute cap, 64 minutes into the
Gradle step, with no test report — the step was still running, so steps 6-11
(lint reports, test report, APK uploads) never ran.

Not a test failure, and not a slow runner. On main the same step takes ~46
minutes, using 76% of the budget. PR runs set `cache-read-only`, so they
restore main's Gradle cache and never save one; a PR touching `quartz` or
`commons` invalidates most of what that cache holds downstream and rebuilds it
cold. Measured across this PR's runs, every job takes 2-3x its main-branch
time — Windows desktop 10m to 21m, macOS 8m to 25m, Linux deb 3.5m to 11m.
Android had the least headroom, so it is the one that died.

Re-running would not help: `cache-read-only` means the timed-out attempt saved
nothing, and the next attempt starts from the same main cache.

90 rather than 60. It costs nothing on runs that finish early — the setting
bounds a job, it does not reserve the time — and leaves room for the observed
2x without hiding a genuine hang behind an enormous cap.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AXvKXakvup4inNFfAhhr4L
2026-09-24 01:50:47 +00:00
..
2025-04-12 15:56:51 +01:00