compute-matrix: add 'docs-build' matrix, switch docs builds to RTX PRO 6000 - #627
Merged
Conversation
jameslamb
added
improvement
bdice
reviewed
Sep 4, 2026
| # - some GPU with low queue | ||
| # - latest driver | ||
| # | ||
| - { ARCH: 'amd64', PY_VER: '3.11', CUDA_VER: '12.9.2', LINUX_VER: 'rockylinux8', GPU: 'rtxpro6000', DRIVER: 'latest'} |
Contributor
There was a problem hiding this comment.
I'd like to use some version of CUDA 13 for our docs builds. Python version is less important. We have better coverage of the environments for CUDA 13 and fewer packaging oddities as CUDA 12 gets harder to support.
Member
Author
There was a problem hiding this comment.
Makes sense!
Most of the docs jobs are already using rapidsai/ci-conda:26.10-latest (which is CUDA 13) so I'll just match that.
bdice
changed the title
16 tasks
jameslamb
force-pushed
the
ci/docs-build-matrix
branch
from
September 10, 2026 01:20
7970c16 to
199ac68
Compare
This was referenced Sep 10, 2026
jameslamb
changed the title
jameslamb
marked this pull request as ready for review
September 10, 2026 03:32
jameslamb
requested review from
bdice and
msarahan
and removed request for
a team and
msarahan
September 10, 2026 03:32
Co-authored-by: Bradley Dice <bdice@bradleydice.com>
jameslamb
force-pushed
the
ci/docs-build-matrix
branch
from
September 10, 2026 12:38
199ac68 to
628369f
Compare
Member
Author
|
I've re-targeted this to |
bdice
approved these changes
Sep 10, 2026
Member
Author
|
/merge |
rapids-bot Bot
pushed a commit
to rapidsai/rmm
that referenced
this pull request
Sep 10, 2026
Contributes to rapidsai/build-planning#333 Updates to hopefully reduce how often `docs-build` jobs get stuck waiting for CI runners. * switches those jobs to RTX Pro 6000 runners * uses shared `docs-build` matrix to set job details ## Notes for Reviewers CI will pass here once rapidsai/shared-workflows#627 is merged. Authors: - James Lamb (https://github.com/jameslamb) Approvers: - Bradley Dice (https://github.com/bdice) - Gil Forsyth (https://github.com/gforsyth) URL: #2542
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.
Contributes to rapidsai/build-planning#333
Introduces a
docs-buildmatrix to thecompute-matrixjob, so we can centrally control which runner types are used for docs builds.Notes for Reviewers
Why RTX Pro 6000?
There's less competition for those runners than for L4s, see rapidsai/build-planning#333 for details.
Why centralize here?
Centralizing that choice of runner type would mean that changing it in the future wouldn't require PRs like NVIDIA/cudf#23878 in every repo. I think that's justified here... it's really unlikely that docs builds would be sensitive to the particular details of a runner, as long as it's a GPU RAPIDS supports.
Notes for reviewers
How I tested this
Saw passing builds and the expected behavior on all of these: