elbepack/log.py: use info logging level by default instead of debugging - #476
Closed
kanavin wants to merge 1 commit into
Closed
elbepack/log.py: use info logging level by default instead of debugging#476kanavin wants to merge 1 commit into
kanavin wants to merge 1 commit into
Conversation
Debugging level should never be set by default and should always be an explicit opt-in via a command line option or an environment variable. The reason is that depending on what logging handlers are set up, and how big the debugging output is for particular code paths, the sheer volume of text can overwhelm the machine or the network. The particular issue here is pytest, which sets up its own handlers for logging that *capture all of the logging in RAM* while the test is running. When pytest performs a base image (or cdrom) upload to initvm, which sends chunks of data to the external binascii module, said module logs lots of debugging *for each chunk*. This quickly exhausts the RAM on my laptop, which is a not-unreasonable 16G. Signed-off-by: Alexander Kanavin <alex@linutronix.de>
kanavin
force-pushed
the
add-base-extended-validation-test-tweaks
branch
from
August 12, 2026 10:50
f634200 to
247f957
Compare
Contributor
|
Thanks, applied. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Debugging level should never be set by default and should always be an explicit opt-in via a command line option or an environment variable. The reason is that depending on what logging handlers are set up, and how big the debugging output is for particular code paths, the sheer volume of text can overwhelm the machine or the network.
The particular issue here is pytest, which sets up its own handlers for logging that capture all of the logging in RAM while the test is running. When pytest performs a base image (or cdrom) upload to initvm, which sends chunks of data to the external binascii module, said module logs lots of debugging for each chunk. This quickly exhausts the RAM on my laptop, which is a not-unreasonable 16G.