chore: remove stable install testing from release branch#848
Open
gforsyth wants to merge 2 commits into
Open
Conversation
Contributor
Author
|
Hmm, just realized that the bot will try to forward merge this into |
…i#847) This is a temporary fix for rapidsai#846 to get the nightly tests passing again. There is a larger issue around the mismatch between development dependencies in our testing matrix and the dependency matrix at time of release.
gforsyth
force-pushed
the
remove_stable_install
branch
from
6994c50 to
72c3c5e
Compare
bdice
reviewed
May 28, 2026
Comment on lines
+37
to
+40
| # TODO: add custom dependency matrix for stable install tests | ||
| matrix_filter: map(select(.CUDA_VER != "13.2.0")) | ||
| permissions: | ||
| contents: read |
Contributor
There was a problem hiding this comment.
If you want to skip this test on release branches, you probably want something like this?
if: github.base_ref == 'main'
Contributor
Author
There was a problem hiding this comment.
Good idea -- just pushed that up
Contributor
Author
There was a problem hiding this comment.
Wow, actually I just pushed it to main directly -- need to make sure the permissions on this repo are set correctly...
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.
xref #846
We added stable install tests as part of rapidsai/build-planning#226
The purpose of these tests is to ensure that, as the dependency environment shifts around us, that a new (or existing) user who does a fresh install of RAPIDS using our published commands gets something that is usable.
We have a bit of an issue in that the stable install testing environment is always going to lag our development environment, because we want to test things that are a little bit older.
I have some ideas about how to handle that, but for now, I think there is no reason to keep running these tests on the release branch -- the exact same tests are being run onmainand those will only change once the 26.06 release is out, at which point we'll start running stable install tests against that version.The other option is to add the samematrix_filterthat I used in #847 but I think this approach makes more sense in this scenario.edit: just cherry picking the matrix filter into this PR to avoid forward-merger shenanigans