Closed
Bug 1232623
Opened 9 years ago
Closed 7 years ago
[Mulet] Running `HOST_LOG=stdout make test-integration` doesn't display all the Gecko logs
Categories
(Testing Graveyard :: JSMarionette, defect)
Testing Graveyard
JSMarionette
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: jlorenzo, Unassigned)
Details
STR
1. Modify 1 test to include something like:
> client.executeScript(function() { console.log('CLIENT SIDE') });
2. Run `HOST_LOG=stdout make test-integration`
3. Look at the output
Displayed results
Unlike a regular ADB logcat on device, you only get the Marionette log:
> 1450177130322 Marionette DEBUG conn2 -> Command {id: 43, name: "executeScript", parameters: {"script":"return (function () { console.log('CLIENT SIDE') }.apply(this, arguments));","args":[],"sandbox":"default"}}
Expected results
After the line above, you should also get:
> 1450177130322 Communications: Content JS LOG: CLIENT SIDE
This example shows that we don't get all the logs coming from Gecko even with the logs turned on. Having them can be useful to debug a test that just got broken.
Comment 1•7 years ago
|
||
Bulk closed as part of https://bugzilla.mozilla.org/show_bug.cgi?id=1422750
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Updated•7 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•