-
Notifications
You must be signed in to change notification settings - Fork 107
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
ament_clang_tidy - Fix Reporting when WarningsAsErrors is specified in config #397
ament_clang_tidy - Fix Reporting when WarningsAsErrors is specified in config #397
Conversation
382e730
to
af6c1cb
Compare
hey @mjeronimo, could you take a look when you get a chance? |
c82bd45
to
ff51753
Compare
This looks like a small enough fix and I happen to have been hit by #411 too. @marcoag @clalancette do you think we could get this in any time soon? |
Yeah, this looks reasonable enough. I'm going to rebase it and then run CI on it. |
ff51753
to
9cbb36e
Compare
Thanks for the bump @mhidalgo-bdai , and thanks for merging @clalancette! |
@clalancette thank you! Could we also ask the Mergify bot for a Humble backport? |
@Mergifyio backport humble iron jazzy |
✅ Backports have been created
|
Issue Summary
When
WarningsAsErrors
is specified in.clang-tidy
, this can lead to some failures in result reporting. Specifically, the following test program (src/factorial.cpp):fails with this output:
when running
ament_clang_tidy
.After applying this fix, I get the following output, which is expected
Relevant section of
.clang-tidy
, for reference:Fix
By trying to access the
output
attribute of the raised exception, we can populate the output in cases where exceptions were raised and there was valid output.