Disable failing FJ test on ARM CI #39
Merged
Conversation
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
Contributor
Author
|
/ok to test |
rg20
approved these changes
May 27, 2025
Contributor
Author
|
/ok to test |
Contributor
Author
|
/merge |
1 similar comment
Contributor
Author
|
/merge |
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.
Temporary band-aid for https://github.com/rapidsai/cuopt/issues/2489, as the underlying issue is difficult to debug and possibly a CUB/cuSparse bug
Under high workloads, it appears calls to cusparse's CSR transpose algorithm return an off-by-one error in one of the indices. This only manifests in the ARM CI in the FJ tests on a specific instance. This PR disables the tests on this instance when building on ARM to work around this issue until the root bug is fixed.