Open wmmc88 opened 2 years ago
Thanks for the report @wmmc88. I can see why ament_clang_tidy
behaves like this.
stderr
coming from clang-tidy
processes is flat out ignoredstdout
coming from any clang-tidy
process is ignored if the process exits with a nonzero return codeament_clang_tidy
return codes are decoupled from those of the clang-tidy
processes it invokes(1.) may be adequate, not sure. (2.) and (3.) are bugs, I agree. Bugfixes are most welcome.
This is using the latest master of ament_lint and latest rolling release.
From https://github.com/uwrobotics/uwrt_mars_rover/runs/4834656922?check_suite_focus=true#step:4:1520 :
Exit status 4 indicating 4 clang-tidy violation errors, yet its still reported as a passed test
When running locally using latest rolling binary via
colcon test
:^ same result as CI running it using latest ament_lint master from source
When running locally using latest rolling binary via
ament_clang_tidy
:Prints that theres an error, but
echo $?
still reports 0. Also doesnt print what the errors actually are (and there doesnt seem to be any verbosity option inament_clang_tidy
)Manually invoking the printed clang-tidy commands:
I finally can see the actual errors!
So the two issues I'm looking to get addressed here are failed tests being detected as passed tests, and failed tests not printing out the actual errors.