Use smaller runtime images for non-build CI steps#320
Merged
Conversation
Signed-off-by: Matthew Cong <mcong@nvidia.com>
Signed-off-by: Matthew Cong <mcong@nvidia.com>
99cf479 to
02a5157
Compare
Signed-off-by: Matthew Cong <mcong@nvidia.com>
7eaf34d to
939c602
Compare
Signed-off-by: Matthew Cong <mcong@nvidia.com>
harrism
approved these changes
Nov 4, 2025
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.
Our C++ tests and documentation tests don't run any build steps so the cudnn-devel image pulls in more than we need when the cudnn-runtime image would be sufficient. This saves about a minute of job time and about 5GB in bandwidth for each (uncached) pull.
We can't apply the same optimization to the PyTests because we build wheels to test against during that job.