Skip to content

ci: use ubuntu-latest for meta jobs instead of org-scoped Warp runner label - #13

Open
tialkan wants to merge 1 commit into
bitcoindogmode:31.1-dogmodefrom
tialkan:31.1-dogmode
Open

tialkan wants to merge 1 commit into
bitcoindogmode:31.1-dogmodefrom
tialkan:31.1-dogmode

Conversation

@tialkan

@tialkan tialkan commented Sep 27, 2026

Copy link
Copy Markdown

Summary

  • `runners` and `record-frozen-commit` used `runs-on: ubuntu-slim`, a Warp runner image scoped to the upstream `bitcoin/bitcoin` org.
  • This fork has no access to that runner group, so GitHub failed the whole workflow before scheduling any job (0 jobs, conclusion failure, "workflow file issue" — e.g. run 33050282126 on `dogmode/tx-weight-3900k`).
  • Both jobs only run shell steps, so `ubuntu-latest` works regardless of provider.

Test plan

  • Pushed the same fix to `tialkan/bitcoin`'s `31.1-dogmode`, `dogmode/tx-weight-3900k`, `dogmode/preferential-peering`, `test-addpeeraddress-services` branches — all now schedule jobs instead of failing with 0 jobs.

… label

The runners/record-frozen-commit jobs ran on runs-on: ubuntu-slim, a
custom Warp runner image scoped to the upstream bitcoin/bitcoin org.
This fork has no access to that runner group, so GitHub failed the
whole workflow before scheduling any job (0 jobs, conclusion failure,
"workflow file issue" - e.g. run 33050282126 on dogmode/tx-weight-3900k).

Both jobs only run shell steps, so a standard GitHub-hosted
ubuntu-latest works regardless of provider.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant