Closed Bug 1067363 Opened 10 years ago Closed 10 years ago

Intermittent test_wifi_enable.js | TimeoutException: TimeoutException: Connection timed out

Categories

(Testing :: Marionette Client and Harness, defect)

Product:
Testing
Component:
Marionette Client and Harness
Platform:
x86
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: cbook, Unassigned)

References

(
URL
)

Details

(Keywords: intermittent-failure)

b2g_emulator_vm mozilla-inbound opt test marionette-webapi on 2014-09-15 04:30:15 PDT for push f5ab7e76389e slave: tst-linux64-spot-455 https://tbpl.mozilla.org/php/getParsedLog.php?id=48088244&tree=Mozilla-Inbound TEST-UNEXPECTED-ERROR | test_wifi_enable.js | TimeoutException: TimeoutException: Connection timed out
David, we are getting this a lot. Philor was thinking that this is a dependency problem somewhere but i talked to dave hunt on irc and he was thinking you might have an idea what i going on here. Could you take a look at this failure, thanks!
Flags: needinfo?(dburns)
seems ed found the push that caused the problem and i guess that only need to be reverted than we should be fine or ed ?
Flags: needinfo?(dburns) → needinfo?(emorley)
Discussed in the sheriff meeting, this was likely caused by the reconfig which switched to a new manifest which has the tests in a different order.
Flags: needinfo?(emorley)
Try push which will hopefully confirm that theory: https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=1c0f8e937f3a Of course, if that's green, it only adds more fuel to the fire for hiding them until they aren't so flaky that simply reordering the tests is enough to make them perma-fail.
[Mass Closure] Intermittents that have not been updated in 2 months being closed
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Product: Testing → Remote Protocol
Moving bug to Testing::Marionette Client and Harness component per bug 1815831.
Component: Marionette → Marionette Client and Harness
Product: Remote Protocol → Testing
You need to log in before you can comment on or make changes to this bug.