Updates CI workflow to run on self-hosted runner#7040
Merged
Conversation
singularity101010
approved these changes
Dec 19, 2025
Member
Author
|
Note that this PR accomplishes the objective, which is to start running CI workflows in a self-hosted runner. However, tests seem to be failing in the new environment, and thus the CI workflow itself is failing. I will proceed to merge this change, bypassing the requirement for the CI workflow to be successful, and we should address the test failures in one or more separate PRs. |
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
2 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.
Motivation for features / changes
The standard runners provided by GitHub started running out of space, so we set up self-hosted runners.
By internal policy, these runners cannot publish artifacts, e.g. to PyPI, so the nightly workflows will need to be update to be produced by separate infra, but at least this unblocks CI runs for PRs and such.
This change also removes the BUILD cache that was not actually used before due to misconfiguration issue. To reduce maintenance burden related to internal security policy and processes, the storage bucket that was used for this purpose had public access removed, so we're simply not using this anymore either way.