-
Notifications
You must be signed in to change notification settings - Fork 9
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
Annoying ecbuild warning message from ecbuild #33
Comments
No - I don't think we should. I just did a PR which is going to be very noisy with WARNING and want to use those to go (gradually) update all the places where things have gotten deprecated. I suppose we could make it the default for regular users though. Hiding DEBUG and INFO level is probably fine by default. @aerorahul Your opinion? |
@mathomp4 the |
I don't have a really strong opinion, but OFF seems like it would hide issues for quite some time. If WARNINGs don't really matter, why did anyone bother with the logic in the first place ... |
Or, I suppose why
Actually, it looks like the default value is actually if( NOT DEFINED ECBUILD_LOG_LEVEL )
set(ECBUILD_LOG_LEVEL ${ECBUILD_INFO}) And |
This is not really important (and is part of #7) but I thought I'd ask @tclune and @aerorahul about it.
During the cmake step we see:
Now, we can set
ECBUILD_LOG_LEVEL=ERROR
and we'd not see this. The question is: Should we? @aerorahul Does the JEDI project have an official thought on what level of ecbuild logging to use?The text was updated successfully, but these errors were encountered: