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
Use different logger classes depending on prefix of requested logger #1171
Conversation
This allows external libraries (e.g., GC3Pie) to use the stdlib logging, while EB keeps using its own logging facility.
Automatic reply from Jenkins: Can I test this? |
Jenkins: ok to test |
1 similar comment
Jenkins: ok to test |
Refer to this link for build results (access rights to CI server needed): |
Things are very broken now, it seems... Somehow EasyBuild isn't using an EasyBuildLog instance anymore?
|
Refer to this link for build results (access rights to CI server needed): |
@boegel Fixed now, thanks for the heads-up. |
A lighter-weight alternative to this is in #1179 |
same here as in #1179; this is a very complex workaround while https://github.com/hpcugent/easybuild-framework/pull/1008/files#diff-30c0c724e8b33847f917f22eca0af7a0R57 does the trick as well, and the |
Yes, I agree to closing w/out merging |
As the title says: this allows external libraries (e.g., GC3Pie) to use stdlib logging, while EB continues to use its own logging facility.
It's a hack, however, that involves directly setting a module-level private variable...