test-conda-nightly-env: remove ucx-proc exclusion #742
Conversation
This file contains 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
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
/ok to test |
jameslamb
changed the title
|
/merge |
bdice
approved these changes
Jan 28, 2025
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.
Contributes to rapidsai/build-planning#142
Proposes removing the exclusion for
ucx-procin the CI job that checks that all projects have produced recent-enough nightlies. See that linked issue for much more detail, but in short:ucx-procpackages for 2+ years, since Update to UCX v1.14.0 and configure/build for release conda-forge/ucx-split-feedstock#111ucx-procdependency, and other PRs linked to Removeucx-procconda dependency build-planning#142 have done that for the 25.02 releaseucx-procshould not show up in RAPIDS 25.02 environment solves, and so we don't need to carry an exclusion for it in the testing config