Closed
Bug 1232321
Opened 9 years ago
Closed 6 years ago
[On device] With a fresh build, MarionetteJS takes 5+ minutes to get the first test running (with no feedback)
Categories
(Testing Graveyard :: JSMarionette, defect)
Testing Graveyard
JSMarionette
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: jlorenzo, Unassigned)
References
Details
Attachments
(1 file)
47.14 KB,
text/plain
|
Details |
STR
1. BUILDAPP=device make test-integration
2. Wait until marionette-mocha gets started
Expected results
You have some feedback on the console or you see what's going on the device itself
Actual ones
It seems like something unnecessary times out after 5 minutes.
You have no feedback for 300+ seconds even with NODE_DEBUG=*. The console remains stuck at:
> [marionette-mocha] Mon, 14 Dec 2015 15:40:51 GMT marionette:tcp-sync write { name: 'newSession',
> parameters: { capabilities: { raisesAccessibilityExceptions: false } },
> to: '0' }
In the meantime, the screen remains turned off. So if one didn't use NODE_DEBUG=*, this person could think the device got bricked.
Reproduction rate:
4/4 with a fresh build. Things are faster the second time.
Reporter | ||
Comment 1•9 years ago
|
||
As automation relies on fresh builds, this will hurt the device availability in the testing farm.
Blocks: 1224301
Reporter | ||
Updated•9 years ago
|
Summary: With a fresh build, MarionetteJS takes 5+ minutes to get the first test running (with no feedback) → [On device] With a fresh build, MarionetteJS takes 5+ minutes to get the first test running (with no feedback)
Comment 2•6 years ago
|
||
Bulk closed as part of https://bugzilla.mozilla.org/show_bug.cgi?id=1422750
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Updated•6 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•