-
Notifications
You must be signed in to change notification settings - Fork 202
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
add support for 'devel' log level #1815
Conversation
@wpoely86 please review? The 2nd step here would be to actually switch to using |
@@ -58,6 +59,10 @@ | |||
DRY_RUN_MODULES_INSTALL_DIR = None | |||
|
|||
|
|||
DEVEL_LOG_LEVEL = logging.DEBUG - 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not +1 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, it's a lower logging level; log.devel
messages should not be included when using --debug
, but log.debug
messages should be included when using --devel
(see also the added test)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wpoely86 so, is this good to go?
Thanks for the review @wpoely86! |
Currently, debug logs are very verbose, with lots of information being logged that is only really useful when developing EasyBuild features.
One particular example in the logging by the toolchain mechanism.
With this
devel
log level in place, we could avoid including stuff like this indebug
logs, while avoiding having to remove thelog.debug
statements entirely.Once a review of all current
log.debug
statements is done and the relevant ones are 'downgraded' tolog.devel
, we can consider make debug logging the default in EasyBuild v3.0.0 (potentially combined with zipping logs by default).cc @wpoely86, @ocaisa