RunsOn v3: switch disk=large → volume=80gb#560
Merged
Merged
Conversation
Migrate the RunsOn self-hosted runner labels from the v2 `disk=large` sizing to the v3 `volume=80gb` form across all three RunsOn workflows (ci, cache, publish). `family=` and `image=` are unchanged. Must merge together with this repo's move from the v2 to the v3 RunsOn GitHub App: v2 does not understand `volume=`, and a v3 runner left on `disk=large` boots the image default root volume. Part of QuantEcon/lectures#5 See QuantEcon/meta#322 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the three RunsOn-backed GitHub Actions workflows to use the v3 runner sizing label format (volume=80gb) instead of the v2 format (disk=large), aligning this repo with the v3 RunsOn GitHub App migration and ensuring adequate disk space on provisioned runners.
Changes:
- Switch
runs-onlabel fromdisk=large→volume=80gbinci,cache, andpublishworkflows. - Keep runner
family=andimage=unchanged across all updated workflows.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/ci.yml | Updates RunsOn label to request an 80GB volume on v3 runners for PR builds. |
| .github/workflows/cache.yml | Updates RunsOn label to request an 80GB volume on v3 runners for cache generation. |
| .github/workflows/publish.yml | Updates RunsOn label to request an 80GB volume on v3 runners for tagged release publishing. |
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
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.
Migrate the RunsOn self-hosted runner labels from the v2
disk=largesizing to the v3volume=80gbform across all three RunsOn workflows (ci,cache,publish).family=andimage=are unchanged.This must merge together with this repo's move from the v2 to the v3 RunsOn GitHub App — v2 does not understand
volume=, and a v3 runner left ondisk=largeboots the image's default root volume (GPU jobs can then hit "no space left on device"). The app move (add to v3 / remove from v2) is already done; opening this PR exercisescion the v3 stack.Part of QuantEcon/lectures#5
See QuantEcon/meta#322