build: Treat all warnings as errors#445
Conversation
Use EXTRA_CXXFLAGS="-Werror" for PR builds
4b4d7aa to
c2159c7
Compare
This reverts commit 275e0cc.
|
Ready for review |
|
Any comments from the code owners? |
genevb
left a comment
There was a problem hiding this comment.
To clarify, this allows pre-existing warnings in old codes to not trigger an alert in CI, while new codes will be monitored for such warnings and either fixed or added to this exclusion list?
Is there a clear (documented?) place to make change that would allow someone compiling the whole library to see the warnings for all codes again?
|
Excellent questions, Gene. The answer to the first question is yes, that is how it is intended to work. With only one comment that the goal should be to shrink the exclusion list rather than adding new codes with questionable constructs. Warnings detect real bugs #431 For the second one, no special action needs to be taken, the warnings for the excluded paths will still appear in the build log, they just won't fail CI. |
|
If no more comments can we merge? |
|
@klendathu2k your last word 🥺 |
klendathu2k
left a comment
There was a problem hiding this comment.
Should be fine, and if/when it breaks the build we will fix.
|
Actually is a funny story. |
|
Cool story, wrong thread 🤣 Moved to #436 (comment) |
This reverts commit 15a7e7c.
These changes do not affect how the code is built by default using
consbut allows one to interrupt compilation when the compiler (GCC 4.8.5) produces a warning.The source files matching the regex patterns in
mgr/warnoff_dirs.txtare excluded from the above rule in order to let CI pass with known problems. We hope this will prevent introduction of questionable code in all other directories or new packages.See issue #392