[mozlog] Fix issues with stdout/stderr interleaved log lines and switch uses of print back to log.{info,error}

NEW
Unassigned

Status

Testing
Mozbase
4 years ago
4 years ago

People

(Reporter: emorley, Unassigned)

Tracking

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
In at least bug 828324 (but in a couple of other places too if memory serves), we've had to use print instead of log.{info,error} due to the log output being interleaved.

The inconsistent usage of print vs mozlog not only is sadfaces, but resulted in things like bug 885591 having to add a silent mode to mozcrash, that is otherwise completely unnecessary.

In Jeff's words...

(In reply to Jeff Hammel [:jhammel] from bug 828324 comment #11)
> This can (and should) be fixed from logging.  I'm not entirely sure how, but
> see http://docs.python.org/2/library/logging.handlers.html .
(Reporter)

Comment 1

4 years ago
Note we may also need to stop prefixing the log lines in such a way (ie adding another pipe delimiter) that breaks TBPL test name parsing.
You need to log in before you can comment on or make changes to this bug.