Skip to content

ci: a single GPU run on push, kkt unless offline else occidata - #1010

Merged
ocots merged 1 commit into
mainfrom
ci/gpu-runner-auto
Oct 20, 2026
Merged

ocots merged 1 commit into
mainfrom
ci/gpu-runner-auto

Conversation

@ocots

@ocots ocots commented Oct 20, 2026

Copy link
Copy Markdown
Member

Follows the pilot control-toolbox/CTSolvers.jl#284 (CTActions#114).

  • On a push to main or a tag, test-gpu-main (CTActions ci-gpu.yml) runs the GPU tests on one runner chosen at run time: kkt unless it is offline, else occidata. A busy kkt is waited for.
  • On a pull request the GPU jobs keep their labels (run ci kkt-runner, run ci occidata-runner): either runner can always be asked for.
  • New test-gpu-kkt job (label run ci kkt-runner); the GPU jobs keep the default Julia versions (1.10, 1.13), as the occidata job had.
  • Documentation: gpu_runner: 'auto' (same choice for the GPU pass; the 180 min timeout already covers the occidata fallback).

The choice reads the runners' state as the read-only GitHub App ct-runners (secrets CT_RUNNERS_*); without them it falls back to occidata with a warning.

🤖 Generated with Claude Code

On a push to main or a tag the GPU CI ran on both runners (or only occidata) and waited for the slower. test-gpu-main (CTActions ci-gpu.yml) picks one runner at run time; the kkt and occidata jobs keep their labels on pull requests.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@ocots
ocots merged commit 46034b0 into main Oct 20, 2026
4 checks passed
@ocots
ocots deleted the ci/gpu-runner-auto branch October 20, 2026 15:07
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