Closed
Bug 974734
Opened 11 years ago
Closed 11 years ago
Failing intermittent notifications test
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
1.4 S3 (14mar)
People
(Reporter: kgrandon, Assigned: mikehenrty)
References
Details
(Whiteboard: [systemsfe][p=1])
Attachments
(1 file)
Test is being disabled due to being intermittent.
Notification.get(): "before each" hook:
Error: timeout of 60000ms exceeded
at null.<anonymous> (/home/travis/build/mozilla-b2g/gaia/node_modules/mocha/lib/runnable.js:165:14)
at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)
3) Notification.get(): "after each" hook:
Error: Not connected. To write data you must call connect first.
at TcpSync.send (/home/travis/build/mozilla-b2g/gaia/node_modules/marionette-client/lib/marionette/drivers/tcp-sync.js:93:15)
at Object.send (/home/travis/build/mozilla-b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:455:36)
at Object.Client._sendCommand (/home/travis/build/mozilla-b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:501:19)
at Object.closeDriver (/home/travis/build/mozilla-b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:747:14)
at Object.executeHook (/home/travis/build/mozilla-b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:360:20)
at Object.Client.runHook (/home/travis/build/mozilla-b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:378:7)
at Object.destroySession [as deleteSession] (/home/travis/build/mozilla-b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:757:12)
at Context.<anonymous> (/home/travis/build/mozilla-b2g/gaia/node_modules/marionette-js-runner/lib/runtime/hostmanager.js:102:14)
at Hook.Runnable.run (/home/travis/build/mozilla-b2g/gaia/node_modules/mocha/lib/runnable.js:194:15)
at next (/home/travis/build/mozilla-b2g/gaia/node_modules/mocha/lib/runner.js:257:10)
at Object._onImmediate (/home/travis/build/mozilla-b2g/gaia/node_modules/mocha/lib/runner.js:274:5)
at processImmediate [as _immediateCallback] (timers.js:330:15)
Assignee | ||
Comment 1•11 years ago
|
||
Since we don't specifically have an "after each" hook for this test, my hunch is that this problem is unrelated to the notification tests. I'm going to bulk travis test this, and re-enabled if everything looks ok.
Assignee: nobody → mhenretty
Whiteboard: [systemsfe][p=1]
Target Milestone: --- → 1.4 S3 (14mar)
Assignee | ||
Comment 2•11 years ago
|
||
20/20 on the first try. I think we can re-enable:
https://travis-ci.org/mozilla-b2g/gaia/builds/20572375
Assignee | ||
Comment 3•11 years ago
|
||
Yo K-dawg, I heard you like re-enabling tests, so i re-enabled some tests so you can re-enable tests while you re-enable tests.
Attachment #8391447 -
Flags: review?(kgrandon)
Reporter | ||
Comment 4•11 years ago
|
||
Comment on attachment 8391447 [details] [review]
Github PR, reenable notification tests
Ok - let's re-enable, but if we see it fail again then we should look into it. I haven't seen any tests with this error recently - so maybe it was a temporary thing.
Attachment #8391447 -
Flags: review?(kgrandon) → review+
Reporter | ||
Comment 5•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•