-
Notifications
You must be signed in to change notification settings - Fork 242
Skip a UVM-Heavy Test Under Compute Sanitizer #1400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
/ok to test ec93c12 |
This comment has been minimized.
This comment has been minimized.
ce6b1b5 to
e3183ab
Compare
|
/ok to test e3183ab |
|
/ok to test cb86bd1 |
|
/ok to test 8823fcc |
- Add --durations=0 to CI pytest invocations to report per-test timings. - Add cuda_python_test_helpers.under_compute_sanitizer() and use it to skip the UVM-heavy PatternGen seed test under compute-sanitizer.
8823fcc to
cbe5b2d
Compare
|
/ok to test cbe5b2d |
| "LD:${CUDA_PATHFINDER_TEST_LOAD_NVIDIA_DYNAMIC_LIB_STRICTNESS} " \ | ||
| "FH:${CUDA_PATHFINDER_TEST_FIND_NVIDIA_HEADERS_STRICTNESS}" | ||
| pytest -ra -s -v tests/ |& tee /tmp/pathfinder_test_log.txt | ||
| pytest -ra -s -v --durations=0 tests/ |& tee /tmp/pathfinder_test_log.txt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems reasonable to report test times so that these issues are easier to debug in the future.
|
CI confirms the fix. This test was taking >20min: CI / Test linux-64 / py3.12, 12.9.1, local, l4 (push)Successful in 6m |
|
Longest durations now reported in the test logs: |
|
Summary
Adjust CI to improve debuggability of long-running tests.
Changes
--durations=0to CIpytestinvocations so logs report per-test timings.cuda_core/tests/test_helpers.py::test_patterngen_seedswhen running under compute-sanitizer (detected viacuda_python_test_helpers.under_compute_sanitizer()), since this test can become extremely slow under sanitizer/UVM-heavy behavior.Rationale
test_patterngen_seedsperforms many syncs and host/device-visible memory comparisons; under compute-sanitizer this can balloon to very long runtimes in some CI environments. Skipping it under sanitizer keeps the CI signal while avoiding hour-scale jobs.Test plan