Skip to content

chore(ci): migrate runners to ubuntu-latest, drop macOS build leg#4850

Merged
timwu20 merged 2 commits into
developmentfrom
chore/migrate-ci-runners-to-warp
May 20, 2026
Merged

chore(ci): migrate runners to ubuntu-latest, drop macOS build leg#4850
timwu20 merged 2 commits into
developmentfrom
chore/migrate-ci-runners-to-warp

Conversation

@timwu20
Copy link
Copy Markdown
Contributor

@timwu20 timwu20 commented May 19, 2026

Summary

  • BuildJet hosted runners are gone, and the org's Warp runners weren't picking up queued jobs either — every PR workflow has been hitting the 24h timeout.
  • Switch all runs-on: to GitHub-hosted ubuntu-latest (free for public repos, no provisioning dependency).
  • Drop macos-latest from the build matrix and collapse the single-platform matrix to a plain runs-on.

Trade-offs

  • Three jobs previously sized for 16vcpu (unit-tests, docker-stress, docker-rpc) now run on the standard 2 vCPU / 7 GB runner. They may be slower; revisit with a paid GitHub larger runner if a job consistently bumps into its timeout-minutes.
  • macOS-specific build breakage will no longer be caught in CI. Restore the leg if gossamer needs to ship to macOS again.

The CI=buildjet env var passed to go test in unit-tests.yml and integration-tests.yml is intentionally left alone — it's a signal value read by test code, not a runner reference. Rename in a follow-up if desired.

@timwu20 timwu20 force-pushed the chore/migrate-ci-runners-to-warp branch from 5495f16 to 1fb39c0 Compare May 19, 2026 17:25
BuildJet hosted runners are no longer available, causing all PR
workflows that target `buildjet-*-ubuntu-2204` labels to queue
indefinitely and ultimately fail with a 24h timeout. Warp runners
configured for the org also failed to pick up queued jobs.

Switch every `runs-on:` to GitHub-hosted `ubuntu-latest`, which is
free for public repositories and has no provisioning dependency.
Note that some jobs previously targeted 16vcpu runners (unit-tests,
docker-stress, docker-rpc) and may now run slower on the 2 vCPU /
7 GB standard runners — revisit with a paid larger runner if needed.

Also drop `macos-latest` from the `build` job matrix. No one ships
gossamer to macOS users and the leg consumed CI minutes without
catching anything in recent memory. Collapse the single-platform
matrix to a plain `runs-on: ubuntu-latest`.

The `CI=buildjet` environment variable passed to `go test` in
unit-tests and integration-tests workflows is intentionally
preserved — it's a signal value read by test code, not a runner
reference.
@timwu20 timwu20 force-pushed the chore/migrate-ci-runners-to-warp branch from 1fb39c0 to e86c729 Compare May 19, 2026 17:36
@timwu20 timwu20 changed the title chore(ci): migrate runners from BuildJet to Warp chore(ci): migrate runners to ubuntu-latest, drop macOS build leg May 19, 2026
The unit-tests job's 15-minute job-level and go test internal
timeouts were sized for the previous 16vcpu runner. On the standard
2 vCPU ubuntu-latest runner the suite now takes longer to complete
and is hitting the 15m limit.

Bump both timeouts to 30m.
@timwu20 timwu20 merged commit 04cb96b into development May 20, 2026
22 of 25 checks passed
@timwu20 timwu20 deleted the chore/migrate-ci-runners-to-warp branch May 20, 2026 01:36
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