cccl icon indicating copy to clipboard operation
cccl copied to clipboard
verified publisher icon NVIDIA

[FEA]: Run tests through `compute-sanitizer` in CI

Open alliepiper opened this issue 1 year ago • 3 comments

To check for memory safety, the tests should be run through compute-sanitizer regularly in CI. Due to the expense, this might be best as a nightly/weekly check.

Work is ongoing in #1879.

Related Tasks

  • [ ] https://github.com/NVIDIA/cccl/issues/1888
  • [ ] #1894
  • [ ] #1895
  • [ ] #1897
  • [ ] #1899
  • [ ] #1898
  • [ ] #1896
  • [ ] https://github.com/NVIDIA/cccl/issues/1891
  • [ ] https://github.com/NVIDIA/cccl/issues/1889
  • [ ] #1902
  • [ ] #1892
  • [ ] #1893
  • [ ] #1906
  • [ ] #1903
  • [ ] https://github.com/NVIDIA/cccl/issues/1911
  • [ ] https://github.com/NVIDIA/cccl/issues/1017
  • [ ] https://github.com/NVIDIA/cccl/issues/1887
  • [ ] #1890
  • [ ] https://github.com/NVIDIA/cccl/issues/1917
  • [ ] #1907
  • [ ] #1909
  • [ ] #1910
  • [ ] https://github.com/NVIDIA/cccl/issues/1790
  • [ ] https://github.com/NVIDIA/cccl/issues/725

alliepiper avatar Apr 11 '24 19:04 alliepiper

What I've envisioned with adding nightly/weekly testing is to start by expanding the matrix.yaml file to add top-level nightly: and weekly: matrices alongside the existing pull_request: matrix.

jrhemstad avatar Apr 11 '24 19:04 jrhemstad

Some of them might be harmless. However, it would be great to find a way to appease the compute-sanitizer so that CUDA programmers can trust the NVIDIA compute-sanitizer to identify any potential bugs while using the thrust/cub library. Thank you so much. 👍

lilohuang avatar Jun 25 '24 00:06 lilohuang

@alliepiper FYI I opened another issue for host-side sanitizers https://github.com/NVIDIA/cccl/issues/2241

fbusato avatar Aug 14 '24 19:08 fbusato