Skip to content
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

Ignore clang's summary warning #768

Merged
merged 1 commit into from
May 2, 2016

Conversation

julienmalik
Copy link
Collaborator

This assumes prior text has matched some other warning expression.

This reduces the warnings reported for clang build on the dashboard,
which were caused only by the "XXX warnings generated." message.
For some reason they were not reported when not using ctest launchers.

This commit allows to confidently use ctest launchers to improve
dashboard reports.

This assumes prior text has matched some other warning expression.

This reduces the warnings reported for clang build on the dashboard,
which were caused only by the "XXX warnings generated." message.
For some reason they were not reported when not using ctest launchers.

This commit allows to confidently use ctest launchers to improve
dashboard reports.
@julienmalik
Copy link
Collaborator Author

Now I get, with clang 3.9 on linux, a single warning report :
http://my.cdash.org/viewBuildError.php?type=1&buildid=953326

which is most probably coming from :

/usr/include/assert.h:92:5: note: expanded from macro 'assert'
  ((expr)                                                               \

We could include this as an exception too, but I'm not sure if it is the best move.
Maybe disabling completely the warnings at compile time for thirdparties ? At least when a specific cmake advanced option is ON (OPJ_THIRDPARTY_NO_WARNING or something like this), which we can use on the dashboard ?

@julienmalik julienmalik merged commit da56086 into uclouvain:master May 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants