I’m trying to integrate cuda-memcheck into our unit testing pipeline. Normally, running cuda-memcheck with
results in an exit code which is 0 if no errors were found, and 1 otherwise. This makes verifying the memory check very easy.
This works for all cuda-memcheck tools (including memcheck itself), except the racecheck tool. This tool seems to always exit with return code 0 no matter how many hazards (errors) were found.
Has anyone bumped up against this issue before? As a workaround, I’m looking to parse the text output of the racecheck tool and look for strings indicating that errors were found. However it’d be really nice to have consistent functionality across all tools.