Skip to content

Add compute-sanitizer CI workflows for memcheck, racecheck, and synccheck#1889

Draft
bdice wants to merge 5 commits intorapidsai:mainfrom
bdice:compute-sanitizer
Draft

Add compute-sanitizer CI workflows for memcheck, racecheck, and synccheck#1889
bdice wants to merge 5 commits intorapidsai:mainfrom
bdice:compute-sanitizer

Conversation

@bdice
Copy link
Contributor

@bdice bdice commented Mar 6, 2026

Summary

  • Adds GitHub Actions workflows to run compute-sanitizer with memcheck, racecheck, and synccheck on all libcuvs C++ test executables
  • Adds cuda-sanitizer-api to test dependencies
  • PR jobs temporarily replaced with sanitizer-only jobs for initial testing (to be reverted before merge)

Details

New files:

  • ci/discover_libcuvs_tests.sh — discovers *_TEST executables from the conda package, excludes multi-GPU tests, outputs JSON array
  • ci/run_compute_sanitizer_test.sh — runs compute-sanitizer on a single test with --force-blocking-launches, kernel name exclusion opt-out (_no_sanitize, _no_<tool>), and --track-stream-ordered-races
  • .github/workflows/compute-sanitizer-run.yaml — reusable workflow creating one matrix job per test per tool
  • .github/workflows/compute-sanitizer-trigger.yaml — weekly (Saturday 10:00 UTC) + manual dispatch entry point for all three tools

Modified files:

  • dependencies.yaml — added cuda-sanitizer-api to test_libcuvs
  • .github/workflows/pr.yaml — temporarily runs only sanitizer jobs (other jobs commented out, to be restored before merge)

Modeled after rapidsai/cudf#20542.

@copy-pr-bot
Copy link

copy-pr-bot bot commented Mar 6, 2026

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.

@bdice
Copy link
Contributor Author

bdice commented Mar 6, 2026

/ok to test

@bdice bdice added feature request New feature or request non-breaking Introduces a non-breaking change labels Mar 6, 2026
@bdice bdice self-assigned this Mar 6, 2026
@bdice
Copy link
Contributor Author

bdice commented Mar 6, 2026

/ok to test

@bdice
Copy link
Contributor Author

bdice commented Mar 6, 2026

/ok to test

@bdice
Copy link
Contributor Author

bdice commented Mar 11, 2026

/ok to test

@aamijar
Copy link
Member

aamijar commented Mar 13, 2026

Thanks @bdice, do you think we should also be running compute-sanitizer on the pytests?

@bdice
Copy link
Contributor Author

bdice commented Mar 14, 2026

Thanks @bdice, do you think we should also be running compute-sanitizer on the pytests?

Probably not necessary. The C++ tests should cover it. I think there may be more false positives in the Python side anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature request New feature or request non-breaking Introduces a non-breaking change

Projects

Development

Successfully merging this pull request may close these issues.

2 participants