Skip to content

Replace Buildkite CI with GitHub Actions self-hosted runners#213

Merged
ChrisRackauckas merged 1 commit intoSciML:masterfrom
ChrisRackauckas-Claude:replace-buildkite-with-gha
Mar 19, 2026
Merged

Replace Buildkite CI with GitHub Actions self-hosted runners#213
ChrisRackauckas merged 1 commit intoSciML:masterfrom
ChrisRackauckas-Claude:replace-buildkite-with-gha

Conversation

@ChrisRackauckas-Claude
Copy link
Contributor

Summary

  • Add .github/workflows/GPU.yml for GPU tests on [self-hosted, Linux, X64, gpu] runners
  • Delete .buildkite/pipeline.yml (no longer needed)
  • Existing CPU tests via SciML/.github reusable workflow in Tests.yml remain unchanged

Details

Part of the SciML-wide migration from Buildkite to GitHub Actions self-hosted runners. See https://github.com/ChrisRackauckas/InternalJunk/issues/16 for runner infrastructure details.

The new GPU workflow:

  • Triggers on push/PR to master (ignoring docs changes)
  • Runs on [self-hosted, Linux, X64, gpu] (Tesla T4 on arctic1)
  • 60-minute timeout (was 30 min on Buildkite, increased for safety)
  • Sets GROUP=GPU environment variable for test selection
  • Includes coverage reporting via Codecov

Test plan

  • Verify GPU workflow triggers on this PR
  • Confirm GPU tests pass on self-hosted runner
  • Verify CPU tests (Tests.yml) still pass unchanged

🤖 Generated with Claude Code

Migrate GPU tests from Buildkite to GitHub Actions using self-hosted
runners with the `gpu` label (Tesla T4 on arctic1).

- Add .github/workflows/GPU.yml for GPU tests on [self-hosted, Linux, X64, gpu]
- Delete .buildkite/pipeline.yml

Part of the SciML-wide migration from Buildkite to GitHub Actions
self-hosted runners. See ChrisRackauckas/InternalJunk#16
for runner infrastructure details.

Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@ChrisRackauckas ChrisRackauckas merged commit 7c8cbd4 into SciML:master Mar 19, 2026
26 of 29 checks passed
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.

2 participants