In #119 we introduced configurable logging levels. That means we need to load configuration before we initialize logging. That means these initialization messages are either lost or always printed (depending on which solution we'll chose in D129), but either way they are not correctly controlled by our settings.
I proposed some solution in https://phab.qadevel.cloud.fedoraproject.org/D129?id=367#inline-1140:
I think it's possible to work around this. We should be able to add some custom handler as the first thing when our program starts. That handler would be a temporary storage for "init/bootup" messages. Once we set up the log file properly, this temporary handler would forward all messages it captured into relevant targets (the log file, stdout if applicable, etc) and we would remove it completely.
I'm not sure how hard this is to do. Try to implement it.
This ticket had assigned some Differential requests: D375
Lowering priority. With our solution, all startup messages are logged at least to stderr. That means it will be captured by buildbot, even though some of it won't be in taskotron.log. So while it is unfortunate, the messages can be found elsewhere and therefore this is not of so high priority.
Metadata Update from @kparal: - Issue marked as depending on: #60
Login to comment on this ticket.