Skip to content

flake: test-go-pg (windows) infrastructure issue - setup-ramdisk download 500s #1477

Open

Description

@flake-investigator

CI Run Link: https://github.com/coder/coder/actions/runs/24649396062
Failed Job: test-go-pg (windows-2022) https://github.com/coder/coder/actions/runs/24649396062/job/72068671580

Commit Info:

  • SHA: 7e89534d32df51ca5a3623bf382b0d7d935cb89c
  • Author: Ethan
  • Message: chore: use coder/hc-install fork to fix expired PGP key verification (#24516)

Failure summary

Key failure evidence

# from Setup RAM Disks step
curl: (22) The requested URL returned error: 500
Warning: Problem : HTTP error. Will retry in 5 seconds. 5 retries left.
...
curl: (22) The requested URL returned error: 500
##[error]Process completed with exit code 22.

Download URL in the step:

https://github.com/ArsenalRecon/Arsenal-Image-Mounter/raw/5961f922c5b99ec29acc4af4b60b909b402eed95/Command%20line%20applications/aim_ll.zip

Additional context

  • The job failed before actions/checkout, so downstream steps were skipped and the Upload Datadog action complained about missing checkout. That is a follow-on symptom, not the root cause.

Assignment analysis

  • No test function failed; failure happened in the pre-checkout setup step.
  • Workflow owner fallback:
    • git log --oneline -10 --follow .github/workflows/nightly-gauntlet.yaml
    • Recent non-bot edits to this workflow include Ethan’s CI maintenance changes.
  • Assigning to @ethanndickson as CI workflow maintainer for nightly-gauntlet and setup steps.

Related issues

Reproduction

  • Re-run nightly-gauntlet on main; failure appears during the Windows setup-ramdisk action when downloading Arsenal Image Mounter artifacts.

Possible mitigations

  • Add retry/backoff + mirror/cached artifact for Arsenal-Image-Mounter downloads.
  • Consider hosting the artifacts internally to avoid GitHub 500s.

Activity

  1. ethanndickson commented on Apr 20, 2026

    @ethanndickson
    Member

    If this happens again I'll seriously consider looking at workarounds, otherwise I don't believe it's worth it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions