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
Ensure that InitialConfigurator uses the Quarkus configured min log level #27826
Conversation
...rojects/bootstrap/runner/src/main/java/io/quarkus/bootstrap/logging/InitialConfigurator.java
Show resolved
Hide resolved
I wonder if it would make sense to write a test for this? I.e. it's possible to test a static_init recorder (although it's not very nice) so in theory it could be feasible... OTOH I'm not sure it's worth the effort ;-) |
36c045a
to
9a261f1
Compare
I personally don't think it's worth the effort, although if someone wants to add a test, I won't object :) |
I don't insist, it was just an idea ;-) |
Wondering if bootstrap times improve a little :) |
I wouldn't hold my breath for this :)
Absolutely true |
This comment has been minimized.
This comment has been minimized.
The native test failure seems related. I'll have to have a look on Monday |
…evel This essentially prevents issues like quarkusio#27735 where a piece of Quarkus code executing very early in the startup sequence, would improperly determine the minimum logging level - i.e. ALL was used instead of the Quarkus build configured minimum level.
PR fixed |
9a261f1
to
33b408b
Compare
This essentially prevents issues like #27735 where a piece of Quarkus code executing very early in the startup sequence, would improperly determine the minimum logging level - i.e. ALL was used instead of the Quarkus build configured minimum level.