ci(docs): move the docs build off the retired juliasim-docs runner - #215
Merged
Conversation
The `self-hosted-juliasim-docs` runner label was served by exactly one machine (arctic3), which is now offline and deregistered. Any job targeting that label queues forever with nothing to pick it up. This repo is public, which constrains which replacement is legal: the organisation's `Default` runner group — where every general-purpose ARC scale set lives — is set to `allows_public_repositories: false`, so a public repo cannot schedule onto it at all. The `public` runner group is the one that accepts public repos, and its scale sets carry a `-public` suffix. Point the docs build at `self-hosted-8vcpu-16gb-public`: that group's `-32gb-public` tier is documented as the namespace's memory reserve at `maxRunners: 1`, which a per-PR docs build should not be occupying, whereas `-16gb-public` is its `heavy-compute` tier. The build shells out to `xvfb-run`, which is present in the ARC runner image, so no workflow change is needed for that.
lamdor
force-pushed
the
la/arc-runners
branch
from
September 8, 2026 15:04
033f58e to
45ff76b
Compare
lamdor
marked this pull request as ready for review
September 9, 2026 12:13
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
1 participant
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.
Summary:
The
self-hosted-juliasim-docsrunner label was served by exactly one machine (arctic3), which is now offline and deregistered. Any job targeting that label queues forever with nothing to pick it up.This repo is public, which constrains which replacement is legal: the organisation's
Defaultrunner group — where every general-purpose ARC scale set lives — is set toallows_public_repositories: false, so a public repo cannot schedule onto it at all. Thepublicrunner group is the one that accepts public repos, and its scale sets carry a-publicsuffix. Point the docs build atself-hosted-8vcpu-16gb-public: that group's-32gb-publictier is documented as the namespace's memory reserve atmaxRunners: 1, which a per-PR docs build should not be occupying, whereas-16gb-publicis itsheavy-computetier.The build shells out to
xvfb-run, which is present in the ARC runner image, so no workflow change is needed for that.CI is red, and it is not this change
The runner change works — the job is now scheduled and starts, where before it would have queued forever. It then fails further along, at dependency installation:
That package is in the private JuliaSimRegistry, reached transitively via
ControlSystemsMTK. This workflow never sets up a private registry — it only setsJULIA_PKG_SERVER. This repo's Documentation workflow has failed continuously since February 2026, long before arctic3 went offline, so the failure predates and is independent of this PR. Turning it green needs a separate change to add registry setup, which I have deliberately kept out of this PR to keep the runner migration reviewable on its own.