952763 - DNT marionette orange

Status: RESOLVED DUPLICATE of bug 1005707

(Testing Graveyard :: JSMarionette, defect)

Description

[Gareth Aye [:gaye] (back from PTO)]

1) manipulate do not track settings "before each" hook:
     
  Error: timeout of 10000ms 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)

  2) manipulate do not track settings "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)

Comment 1

[Kevin Grandon :kgrandon]

Appears this is part of an infrastructure bug, let's track it in bug 1005707.