CI: a GitHub outage fails every job at the JDK download #68

New issue

Open

opened 2026-10-03 22:29:58 +00:00 by claude · 0 comments

claude commented

2026-10-03 22:29:58 +00:00

Member

Every job in .github/workflows/ci.yml (lines 41, 76, 111, 151 on main) runs actions/setup-java@v4 with distribution: temurin, java-version: 21. The step resolves the latest 21.x and downloads it from github.com on every job. The JDK is not cached and the version is not fixed.

Evidence: on 2026-10-03 between 21:51 and 21:54 UTC, 7 jobs of PRs #64, #65 and #66 (runs 1087, 1088, 1089) failed in "Set up Java 21" with ::error::Unexpected HTTP response: 503 after three retries. No code was compiled or tested. A re-run is the only fix.

Possible directions (not decided): cache the JDK (cache input or a tool cache on the runner), use a runner image that already has JDK 21, or fix the version so a cached download is reused. Also, setup-java@v4 is deprecated (log warning: migrate to v5).

🤖 Generated with Claude Code

Every job in `.github/workflows/ci.yml` (lines 41, 76, 111, 151 on main) runs `actions/setup-java@v4` with `distribution: temurin`, `java-version: 21`. The step resolves the latest 21.x and downloads it from github.com on every job. The JDK is not cached and the version is not fixed. Evidence: on 2026-10-03 between 21:51 and 21:54 UTC, 7 jobs of PRs #64, #65 and #66 (runs 1087, 1088, 1089) failed in "Set up Java 21" with `::error::Unexpected HTTP response: 503` after three retries. No code was compiled or tested. A re-run is the only fix. Possible directions (not decided): cache the JDK (`cache` input or a tool cache on the runner), use a runner image that already has JDK 21, or fix the version so a cached download is reused. Also, `setup-java@v4` is deprecated (log warning: migrate to v5). 🤖 Generated with [Claude Code](https://claude.com/claude-code)