Skip to content

Commit 058e832

Browse files
authored
Add force-blocking-launches to run_compute_sanitizer_test script (#20962)
The weekend compute-sanitizer runs are failing with segfaults which cannot be reproduced locally. It is possible that `compute-sanitizer` itself is running out of memory: https://docs.nvidia.com/compute-sanitizer/ComputeSanitizer/index.html#memory-footprint Adding the `--force-blocking-launches` as recommended in this PR. Authors: - David Wendt (https://github.com/davidwendt) Approvers: - James Lamb (https://github.com/jameslamb) URL: #20962
1 parent 8787a9f commit 058e832

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

ci/run_compute_sanitizer_test.sh

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
#!/bin/bash
2-
# SPDX-FileCopyrightText: Copyright (c) 2025, NVIDIA CORPORATION.
2+
# SPDX-FileCopyrightText: Copyright (c) 2025-2026, NVIDIA CORPORATION.
33
# SPDX-License-Identifier: Apache-2.0
44

55
set -euo pipefail
@@ -68,6 +68,7 @@ fi
6868
# Run compute-sanitizer on the specified test
6969
compute-sanitizer \
7070
--tool "${TOOL_NAME}" \
71+
--force-blocking-launches \
7172
--kernel-name-exclude kns=nvcomp,kns=zstd \
7273
--error-exitcode=1 \
7374
"${TEST_EXECUTABLE}" \

0 commit comments

Comments
 (0)