Skip to content

ci: Go toolchain and module downloads fail transiently; cache or retry #349

Description

@teemow

Problem

Two CI jobs went red this week on network transients while fetching Go bits, each on a change that does not touch the code under test, each green on rerun:

On this strict-base rebase line a red job costs a rerun and, once a merge lands ahead, a rebuilt pull request, so one failed download is paid more than once.

Proposed solution

Make the Go downloads independent of one network round: cache the toolchain and the module cache (actions/setup-go with cache: true keyed on go.sum, or actions/cache over GOMODCACHE/GOCACHE), and run go mod download with a bounded retry before the build and the manifest generation. A fork-infrastructure change (workflow files only), squashed per FORK.md.

Acceptance criteria

  • build (golang-adk) and manifests-check take their toolchain and modules from the cache on a warm run (visible in the job log).
  • A single failed download no longer fails the job: the step retries, or the cache serves it.
  • No change to the code under test.

Written by an agent.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    • Status
      Inbox 📥

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions