Use larger runners for nightly CI builds#978
Merged
mhucka merged 4 commits intotensorflow:masterfrom Feb 4, 2026
Merged
Conversation
d1dcaa6 to
b10b23e
Compare
The ml-build Docker image selected by the tag used here is Ubuntu 22.04 That image is created by ci/official/containers/ml_build/Dockerfile in the TensorFlow GitHub repository (specifically, the version of the file as it existed at git commit 1b4ef03f370aa7b266722e1055800275a2db11d0).
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.
The nightly test job is failing due to running out of disk space. (It's the same problem we had recently with the CI checks workflow.) This PR updates the jobs to use the larger self-hosted runners from Google ML Velocity.
Details about the Docker image we are currently: