Hi Martijn,

Both of tests are known to be terribly intermittent and flaky, I would use
different test files to see what happens. Or simply try and run all to see
if it works.

cheers,
--aus

On Tue, Nov 24, 2015 at 8:28 AM, Martijn <[email protected]> wrote:

>
>
> On Sat, Nov 21, 2015 at 2:23 AM, Aus Lacroix <[email protected]> wrote:
>
>> Hi All,
>>
>> This is happening today. Right after the timestamp on this message. If
>> you're reading it after the timestamp, you will need to update your local
>> node install to 4.2.2 (LTS). Or give NVM a shot.
>>
>> Here's where to get it -- https://nodejs.org/en/download/
>>
>> For you package manager users out there --
>> https://nodejs.org/en/download/package-manager/
>>
>> After updating you *MUST* |make really-clean|. I would also suggest
>> running |npm cache clear|.
>>
>
>
> Ok, I did:
> brew install homebrew/versions/node4-lts
> make really-clean
> npm cache clear
>
> Then I tried to run one of the tests:
> TEST_FILES=./apps/system/test/marionette/app_window_mananger_pinned_sites_test.js
> make test-integration
>
> I got this error:
>   0 passing (1m)
>   2 failing
>
>   1) AppWindowManager - Pinning sites Pinning unscoped "before each" hook:
>
>   Error: timeout exceeded!
>       at Object.Client.waitForSync
> (/Users/mwargers/B2G/gaia_clean/node_modules/marionette-client/lib/marionette/client.js:760:16)
>       at Object.Client.waitFor
> (/Users/mwargers/B2G/gaia_clean/node_modules/marionette-client/lib/marionette/client.js:726:60)
>       at Object.MarionetteHelper.waitForElementToDisappear
> (/Users/mwargers/B2G/gaia_clean/node_modules/marionette-helper/index.js:192:17)
>       at Object.openAndPinSite [as openAndPinSiteFromBrowser]
> (/Users/mwargers/B2G/gaia_clean/apps/system/test/marionette/lib/pinning_the_web.js:77:24)
>       at pinAndKill
> (/Users/mwargers/B2G/gaia_clean/apps/system/test/marionette/app_window_mananger_pinned_sites_test.js:36:13)
>       at Context.<anonymous>
> (/Users/mwargers/B2G/gaia_clean/apps/system/test/marionette/app_window_mananger_pinned_sites_test.js:74:7)
>       at callFn
> (/Users/mwargers/B2G/gaia_clean/node_modules/mocha/lib/runnable.js:250:21)
>       at Hook.Runnable.run
> (/Users/mwargers/B2G/gaia_clean/node_modules/mocha/lib/runnable.js:243:7)
>       at next
> (/Users/mwargers/B2G/gaia_clean/node_modules/mocha/lib/runner.js:258:10)
>       at Immediate._onImmediate
> (/Users/mwargers/B2G/gaia_clean/node_modules/mocha/lib/runner.js:275:5)
>       at processImmediate [as _immediateCallback] (timers.js:383:17)
>
>   2) AppWindowManager - Pinning sites Pinning scoped "before each" hook:
>
>   Error: timeout exceeded!
>       at Object.Client.waitForSync
> (/Users/mwargers/B2G/gaia_clean/node_modules/marionette-client/lib/marionette/client.js:760:16)
>       at Object.Client.waitFor
> (/Users/mwargers/B2G/gaia_clean/node_modules/marionette-client/lib/marionette/client.js:726:60)
>       at Object.MarionetteHelper.waitForElementToDisappear
> (/Users/mwargers/B2G/gaia_clean/node_modules/marionette-helper/index.js:192:17)
>       at Object.openAndPinSite [as openAndPinSiteFromBrowser]
> (/Users/mwargers/B2G/gaia_clean/apps/system/test/marionette/lib/pinning_the_web.js:77:24)
>       at pinAndKill
> (/Users/mwargers/B2G/gaia_clean/apps/system/test/marionette/app_window_mananger_pinned_sites_test.js:36:13)
>       at Context.<anonymous>
> (/Users/mwargers/B2G/gaia_clean/apps/system/test/marionette/app_window_mananger_pinned_sites_test.js:167:7)
>       at callFn
> (/Users/mwargers/B2G/gaia_clean/node_modules/mocha/lib/runnable.js:250:21)
>       at Hook.Runnable.run
> (/Users/mwargers/B2G/gaia_clean/node_modules/mocha/lib/runnable.js:243:7)
>       at next
> (/Users/mwargers/B2G/gaia_clean/node_modules/mocha/lib/runner.js:258:10)
>       at Immediate._onImmediate
> (/Users/mwargers/B2G/gaia_clean/node_modules/mocha/lib/runner.js:275:5)
>       at processImmediate [as _immediateCallback] (timers.js:383:17)
>
>
>
>
> npm ERR! Darwin 14.5.0
> npm ERR! argv "/usr/local/Cellar/node4-lts/4.2.2/bin/node"
> "/usr/local/bin/npm" "run" "marionette" "--" "--buildapp=desktop"
> "--reporter=spec"
> npm ERR! node v4.2.2
> npm ERR! npm  v2.14.7
> npm ERR! code ELIFECYCLE
> npm ERR! [email protected] marionette: `gaia-marionette "--buildapp=desktop"
> "--reporter=spec"`
> npm ERR! Exit status 2
> npm ERR!
> npm ERR! Failed at the [email protected] marionette script 'gaia-marionette
> "--buildapp=desktop" "--reporter=spec"'.
> npm ERR! This is most likely a problem with the gaia package,
> npm ERR! not with npm itself.
> npm ERR! Tell the author that this fails on your system:
> npm ERR!     gaia-marionette "--buildapp=desktop" "--reporter=spec"
> npm ERR! You can get their info via:
> npm ERR!     npm owner ls gaia
> npm ERR! There is likely additional logging output above.
>
> npm ERR! Please include the following file with any support request:
> npm ERR!     /Users/mwargers/B2G/gaia_clean/npm-debug.log
> make: *** [test-integration-test] Error 1
>
> npm-debug.log shows this:
> 0 info it worked if it ends with ok
> 1 verbose cli [ '/usr/local/Cellar/node4-lts/4.2.2/bin/node',
> 1 verbose cli   '/usr/local/bin/npm',
> 1 verbose cli   'run',
> 1 verbose cli   'marionette',
> 1 verbose cli   '--',
> 1 verbose cli   '--buildapp=desktop',
> 1 verbose cli   '--reporter=spec' ]
> 2 info using [email protected]
> 3 info using [email protected]
> 4 verbose run-script [ 'premarionette', 'marionette', 'postmarionette' ]
> 5 info premarionette [email protected]
> 6 info marionette [email protected]
> 7 verbose unsafe-perm in lifecycle true
> 8 info [email protected] Failed to exec marionette script
> 9 verbose stack Error: [email protected] marionette: `gaia-marionette
> "--buildapp=desktop" "--reporter=spec"`
> 9 verbose stack Exit status 2
> 9 verbose stack     at EventEmitter.<anonymous>
> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:214:16)
> 9 verbose stack     at emitTwo (events.js:87:13)
> 9 verbose stack     at EventEmitter.emit (events.js:172:7)
> 9 verbose stack     at ChildProcess.<anonymous>
> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:24:14)
> 9 verbose stack     at emitTwo (events.js:87:13)
> 9 verbose stack     at ChildProcess.emit (events.js:172:7)
> 9 verbose stack     at maybeClose (internal/child_process.js:818:16)
> 9 verbose stack     at Process.ChildProcess._handle.onexit
> (internal/child_process.js:211:5)
> 10 verbose pkgid [email protected]
> 11 verbose cwd /Users/mwargers/B2G/gaia_clean
> 12 error Darwin 14.5.0
> 13 error argv "/usr/local/Cellar/node4-lts/4.2.2/bin/node"
> "/usr/local/bin/npm" "run" "marionette" "--" "--buildapp=desktop"
> "--reporter=spec"
> 14 error node v4.2.2
> 15 error npm  v2.14.7
> 16 error code ELIFECYCLE
> 17 error [email protected] marionette: `gaia-marionette "--buildapp=desktop"
> "--reporter=spec"`
> 17 error Exit status 2
> 18 error Failed at the [email protected] marionette script 'gaia-marionette
> "--buildapp=desktop" "--reporter=spec"'.
> 18 error This is most likely a problem with the gaia package,
> 18 error not with npm itself.
> 18 error Tell the author that this fails on your system:
> 18 error     gaia-marionette "--buildapp=desktop" "--reporter=spec"
> 18 error You can get their info via:
> 18 error     npm owner ls gaia
> 18 error There is likely additional logging output above.
> 19 verbose exit [ 1, true ]
>
> What am I doing wrong?
>
> Regards,
> Martijn
>
>
>
>> Please
>>
>> word,
>> --aus
>>
>>
>> On Wed, Nov 11, 2015 at 4:15 PM, Aus Lacroix <[email protected]> wrote:
>>
>>> Hi All,
>>>
>>> As many of you may know, we've been stuck on node 0.12 for quite a long
>>> time.
>>>
>>> Many efforts have gone in to update _the world_ to run node 4.2.2 (LTS).
>>>
>>> See bug https://bugzilla.mozilla.org/show_bug.cgi?id=1223661 if you're
>>> extra curious about what was updated.
>>>
>>> *We will be attempting to land this as soon as the reviews are
>>> completed.*
>>>
>>> *I'll let this list know when it's landed*, but, in short, if no tests
>>> run, you probably need to update your version of node and make
>>> really-clean. :)
>>>
>>> nvm (https://github.com/creationix/nvm) provides an interesting toolbox
>>> to deal with multiple versions of node installed locally. I suggest you use
>>> it if you need more than one version present on your system at a time.
>>>
>>> Garent Aye also wrote something called envy that can help manager
>>> multiple node versions.
>>>
>>> I *highly* recommend dealing with this upgrade sooner rather than later.
>>> :)
>>>
>>> word,
>>> --aus
>>>
>>
>>
>> _______________________________________________
>> dev-fxos mailing list
>> [email protected]
>> https://lists.mozilla.org/listinfo/dev-fxos
>>
>>
>
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos

Reply via email to