Closed
Bug 1275270
Opened 9 years ago
Closed 8 years ago
Missing logging in listener.js
Categories
(Remote Protocol :: Marionette, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1357407
People
(Reporter: ato, Unassigned)
Details
Log statements in command implementations, possibly just those using the new dispatching technique, cause log statements not to get propagated to stdout.
The logger.debug("listener.js loaded") statement near the top of the file _does_ get printed and so does the logging statements I put into the dispatch() function, but only for the _first_ command.
It does not appear to be related to generator functions.
This obviously needs more investigation.
Comment 1•9 years ago
|
||
Interestingly we have similar issues with gecko logging for update tests on Windows only. See bug 1008135.
Reporter | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Comment 3•8 years ago
|
||
No, this is a dupe of bug 1357407.
Updated•2 years ago
|
Product: Testing → Remote Protocol
You need to log in
before you can comment on or make changes to this bug.
Description
•