flake: CI failure in main - gen job (pnpm setup) and build job (Java setup)

[blink-so]

CI Failure Report

Workflow: ci
Committer: BrunoQuaresma
Commit: d77c3d0226c984902c383fc36991127c699747da
View failure: https://github.com/coder/coder/actions/runs/17135119572

Failure Summary

The CI pipeline failed on main branch with multiple job failures:

1. gen job - Failed during "Setup Node" step with pnpm installation timeout
2. build job - Failed during "Setup Java" step
3. required job - Failed due to gen job failure

Detailed Analysis

Gen Job Failure

• Step: Setup Node (pnpm/action-setup)
• Error: ERR_PNPM_META_FETCH_FAIL GET https://registry.npmjs.org/pnpm: request to https://registry.npmjs.org/pnpm failed, reason:
• Root Cause: Network timeout when fetching pnpm from npm registry
• Duration: Failed after multiple retries (10s, 1min timeouts)

Build Job Failure

• Step: Setup Java (actions/setup-java)
• Error: Java setup failed during "Trying to resolve the latest version from remote"
• Root Cause: Likely network/timeout issue similar to pnpm failure

Impact

• Required checks failed, blocking the main branch
• Multiple infrastructure-related failures suggest runner or network issues

Investigation Notes

• No existing similar issues found in recent history
• This appears to be an infrastructure/network flake rather than code-related
• The failing commit (d77c3d0226c984902c383fc36991127c699747da) was a feature change unrelated to CI setup
• Last modification to setup-node action was by ケイラ (mckayla@hey.com) in commit 5c88d93207b15a404eae47c0c09e150d16336407

Recommendation

This appears to be a transient infrastructure issue. Consider:

1. Re-running the failed jobs
2. Monitoring for similar network timeout patterns
3. Potentially adding retry logic or timeout adjustments for setup steps

Assignee

Assigning to @mckayla-coder as the last person to modify the setup-node action configuration.

[ethanndickson]

looks like a github issue