Make dump, console.log, and reportError always go to logcat in Marionette emulator tests

NEW
Assigned to

Status

()

Core
General
6 years ago
6 years ago

People

(Reporter: jgriffin, Assigned: philikon)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
Currently, dump(), console.log, and reportError don't always go consistently to logcat when running Marionette tests in B2G emulators.  This is thought to be because there are many separate implementations of dump, and not all have been updated to go to logcat.

One specific case where this doesn't happen is in code loaded by dbg-server.js, including marionette-actors.js, and thus any script executed in a chrome context by execute_script() or execute_async_script().  

dbg-server.js is loaded by this code, in a sandbox with a separate system principle:

http://mxr.mozilla.org/mozilla-central/source/toolkit/devtools/debugger/server/dbg-server.jsm#72
(Reporter)

Updated

6 years ago
Duplicate of this bug: 752116
You need to log in before you can comment on or make changes to this bug.