Closed Bug 897135 Opened 7 years ago Closed 7 years ago

Switch Marionette logging level to trace

Categories

(Testing :: Marionette, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED
mozilla25

People

(Reporter: jgriffin, Assigned: jgriffin)

Details

Attachments

(1 file)

Many B2G tests are randomly failing with:

08:56:01     INFO -  I/Gecko   (   45): Handler function DebuggerTransport instance's this.hooks.onPacket threw an exception: TypeError: self.hooks is null
08:56:01     INFO -  I/Gecko   (   45): Call stack:
08:56:01     INFO -  I/Gecko   (   45): DT__processIncoming/<@chrome://marionette/content/marionette-server.js -> resource://gre/modules/devtools/server/transport.js:183
08:56:01     INFO -  I/Gecko   (   45): makeInfallible/<@chrome://marionette/content/marionette-server.js -> resource://gre/modules/devtools/DevToolsUtils.js:61

This is an error in the debugger transport; it looks like something is interrupting the socket between client and server.  To help diagnose, let's switch Marionette's log level to "Trace", which will cause the dumpn() statements in transport.js to get logged.
Attachment #779880 - Flags: review?(wlachance)
Comment on attachment 779880 [details] [diff] [review]
Switch Marionette's log level to Trace,

Review of attachment 779880 [details] [diff] [review]:
-----------------------------------------------------------------

As discussed on irc, we'd like to make this configurable, but this will do to investigate the issue in question.
Attachment #779880 - Flags: review?(wlachance) → review+
https://hg.mozilla.org/mozilla-central/rev/b95d233400d6
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.