Switch CI from Buildkite to GitHub Actions - #106
Merged
Conversation
Port the benchmark pipeline to GitHub-hosted runners using the open-source Julia actions (julia-actions/setup-julia, julia-actions/cache), replacing the Buildkite pipeline that ran on the private juliaecosystem queue. The matrix (nightly x serial/multithreaded/all plus slow/bigint), the 60-minute timeout, the [skip tests] escape hatch and the results.csv artifact are carried over unchanged. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CRecnQX4hRN8ecrgHytLHT
Member
Author
|
Note for merging: GitHub Actions appears to be disabled for this repository (no workflows register and the head commit gets zero check runs — only Buildkite responded to the PR). A repo/org admin needs to enable it under Settings → Actions → General before or when this merges, or the new workflow will silently never run. |
Collaborator
|
do we need a token? |
CI on hosted runners is meant to check that every benchmark still runs, not to measure performance. The previous run died in `append` when the 7 GB runner hit memory pressure and the thrashing callback abort()ed. `util/utils.jl` now reads GCBENCH_SCALE (default 1 = full workload) and exposes `scaled(n)` / `scaled_log2(k)`; each benchmark's top-level size goes through one of them. The GitHub workflow sets GCBENCH_SCALE=0.05 and `--runs=1`, which brings every job to ~1 minute and ~1 GB peak RSS. Running without the variable is unchanged. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Thanks @gbaraldi @oscardssmith ! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ports the benchmark pipeline to GitHub-hosted runners using the open-source Julia actions (
julia-actions/setup-julia@v2,julia-actions/cache@v2), replacing the Buildkite pipeline that ran on the privatejuliaecosystemqueue.Carried over unchanged from the Buildkite matrix:
[skip tests]commit-message escape hatchresults.csvuploaded as an artifact per matrix entry (namedresults-<version>-<benchmark>-<category>)Additions that come free with GHA:
pull_requesttriggers (Buildkite only ran on push), per-ref concurrency cancellation, and the Julia depot cache between runs.One honest caveat for reviewers: GitHub-hosted runners are shared 4-vCPU VMs, so timing numbers will be noisier than on the Buildkite fleet — this CI is best read as a does-it-run/regression smoke check, with real measurements still done on dedicated hardware.
Disclosure: this PR was written with the assistance of generative AI (Claude).
🤖 Generated with Claude Code