Repository navigation
Conversation
vyasr
marked this pull request as draft
October 8, 2026 20:47
Contributor
Author
|
Closing in favor of implementing the complementary CUDA coverage policy entirely in cuDF using the existing compute-matrix and matrix_filter interfaces. We accept independently resolved matrix snapshots within a workflow run, so no shared-workflows API changes are needed. |
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.
Description
Add a reusable resolver that returns wheel-test and Conda Python-test matrices from one preparation of the shared matrix definitions. Callers can plan complementary coverage using a single snapshot, without copying these definitions into downstream repositories.
The wheel and Conda Python test workflows accept an optional
resolved-matrixJSON input. Matrix validation, existing filters, and pure-package selectors remain centralized in the shared implementation. When no snapshot is supplied, callers retain the existing resolution behavior. Supplied snapshots do not reread mutable matrix definitions.Regression tests cover default callers, filtering, pure-package selectors, duplicate matrix types, malformed inputs, and reuse despite changed source definitions. The resolver and consumer should use the same shared-workflows revision.
Pin the existing proxy-cache actions to their current revision to satisfy the repository's pinned security checks on the affected workflows.