Planets has to be aligned in order to run Gij locally

[Tim Guan-tin Chien]

After repeating trial and error, I realized Gij only behaves if the
following runtime has the exact version installed on your machine:

node ~= 0.10
npm ~= 2
python ~= 2.7
virtualenv ~= 13.1.0

This is an unfriendly setup and require experience engineer to dive
into the log to find out why, step-by-step. Particularly, the npm
required is not the version preloaded with node v0.10.

I have previously filed
https://bugzilla.mozilla.org/show_bug.cgi?id=1170426 on this.

Can we get a friendlier warning or error on this version requirements? Thanks.


Tim

[Tim Guan-tin Chien]

BTW, I am sorry I have created yet another thread for this issue. I
know it's been asked many times. Just want to know if we could have a
better developer experience here.

Thanks!

[Gareth Aye]

Not a problem. This is obviously a real pain point for developers and an area that we need to improve. There are two directions that we can go from here:

1. Only support developing with specific versions of our global dependencies. Fail when those dependency versions aren't satisfied with helpful error messages

2. Try to expand our support to a larger range of versions for our global dependencies.

The tradeoff is that, while supporting more versions is easier and more flexible for developers, we'll also need to start running tests on those versions. Suppose we supported

- w versions of nodejs >= 0.10 (very unlikely we'll ever do <0.10)

- x versions of npm >= 2 (versions before 2 don't support local modules)

- y versions of python >= 2.7 (mozbase requires python>=2.7[0])

- z versions of virtualenv >= 12 (virtualenv version history is... murky before 12)

Then we have to run w*x*y*z as many tests on ci as we were previously. That could get out of hand pretty quickly :). I could see trying to support both nod...@0.10 and nod...@0.12 as well as npm@2 and npm@3, but running 4x as many tests on ci might come with a significant cost in resources and testing time. I think a more realistic short-term goal would be locking down our global dependency versions and failing when they aren't satisfied. I wrote a utility[1] a couple weeks ago to do node and npm version management with an in-tree profile, but we could also very easily have the task runner[2] that aus is working on integrating into gaia fail to run any tasks if our global dependencies don't have the target versions.

Would it work for you and others to lock down global dependencies for development to no...@0.10, npm@2, python@2.7, and virtualenv@13?

0. https://wiki.mozilla.org/Auto-tools/Projects/Mozbase
1. https://github.com/gaye/envy
2. https://github.com/lightsofapollo/exhibition

[Tim Guan-tin Chien]

On Wed, Jul 1, 2015 at 9:20 PM, Gareth Aye <ga...@mozilla.com> wrote:
> Would it work for you and others to lock down global dependencies for
> development to no...@0.10, npm@2, python@2.7, and virtualenv@13?

WFM if we explicitly fail when the versions don't match, thanks!

[Staś Małolepszy]

What's holding us back from upgrading to node 0.12? The default npm version for node 0.10 is 1.4, and if you want to have both 0.10 and 0.12 on your system, making 0.10 use npm 2.0 requires additional work.  It's not hard, but represents an additional step which might turn people away.

_______________________________________________
dev-gaia mailing list
dev-...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-gaia

[Gareth Aye]

The integration tests have been working for me locally on node 0.12 for at least the past month (I'm on Ubuntu 14.04). Other people claim to be running into issues though?

[Benjamin Francis]

I am still unable to run our integration tests locally, either on OS X or Linux. On OS X I seem to have a problem with virtualenv and on Linux I have a separate problem causing all the tests to time out, possibly related to webapps-registry-ready.

I'm using the exact supposedly planet aligning node/npm/python/virtualenv combination that Tim describes but am still not having any luck. Gareth made a gallant effort at trying to help me debug over IRC yesterday but still no luck.

I'm just wondering, am I the only person who is having these problems, or are integration tests this unreliable for other people too?

This has been blocking me from landing any patches all week :(

Ben

[Alberto Pastor]

I always need to make really-clean, make test-integration (it fails), npm install, and then run again make test-integration.

: /

[Alexandre Lissy]

Le 08/07/2015 16:51, Benjamin Francis a écrit :
> I am still unable to run our integration tests locally, either on OS X
> or Linux. On OS X I seem to have a problem with virtualenv and on Linux
> I have a separate problem causing all the tests to time out, possibly
> related to webapps-registry-ready.
>
> I'm using the exact supposedly planet aligning
> node/npm/python/virtualenv combination that Tim describes but am still
> not having any luck. Gareth made a gallant effort at trying to help me
> debug over IRC yesterday but still no luck.
>
> I'm just wondering, am I the only person who is having these problems,
> or are integration tests this unreliable for other people too?

I had tons of issues. Those magically solved last time after loosing
hours/days on this.

I fear the next time I have to work/debug on integration tests.

>
> This has been blocking me from landing any patches all week :(
>
> Ben
>
>
> On 1 July 2015 at 15:14, Gareth Aye <ga...@mozilla.com

> <mailto:ga...@mozilla.com>> wrote:
>
> The integration tests have been working for me locally on node 0.12
> for at least the past month (I'm on Ubuntu 14.04). Other people
> claim to be running into issues though?
>
> On Wed, Jul 1, 2015 at 9:52 AM, Staś Małolepszy <st...@mozilla.com
> <mailto:st...@mozilla.com>> wrote:
>
> What's holding us back from upgrading to node 0.12? The default
> npm version for node 0.10 is 1.4, and if you want to have both
> 0.10 and 0.12 on your system, making 0.10 use npm 2.0 requires
> additional work. It's not hard, but represents an additional
> step which might turn people away.
>
> On Wed, Jul 1, 2015 at 3:46 PM, Tim Guan-tin Chien
> <timd...@mozilla.com <mailto:timd...@mozilla.com>> wrote:
>
> On Wed, Jul 1, 2015 at 9:20 PM, Gareth Aye <ga...@mozilla.com
> <mailto:ga...@mozilla.com>> wrote:
> > Would it work for you and others to lock down global dependencies for
> > development to no...@0.10, npm@2, python@2.7, and virtualenv@13?
>
> WFM if we explicitly fail when the versions don't match, thanks!
> _______________________________________________
> dev-gaia mailing list

> dev-...@lists.mozilla.org <mailto:dev-...@lists.mozilla.org>

> https://lists.mozilla.org/listinfo/dev-gaia
>
>
>
>
> _______________________________________________
> dev-gaia mailing list

> dev-...@lists.mozilla.org <mailto:dev-...@lists.mozilla.org>

[Gareth Aye]

Alberto - I think I may have fixed your issue sometime during the work week. Can you give that a try again and let us know if you still have the same problem?

On Wed, Jul 8, 2015 at 10:53 AM, Alberto Pastor <apa...@mozilla.com> wrote:

I always need to make really-clean, make test-integration (it fails), npm install, and then run again make test-integration.

: /

On 8 Jul 2015, at 16:51, Benjamin Francis <bfra...@mozilla.com> wrote:

I am still unable to run our integration tests locally, either on OS X or Linux. On OS X I seem to have a problem with virtualenv and on Linux I have a separate problem causing all the tests to time out, possibly related to webapps-registry-ready.

I'm using the exact supposedly planet aligning node/npm/python/virtualenv combination that Tim describes but am still not having any luck. Gareth made a gallant effort at trying to help me debug over IRC yesterday but still no luck.

I'm just wondering, am I the only person who is having these problems, or are integration tests this unreliable for other people too?

This has been blocking me from landing any patches all week :(

Ben

On 1 July 2015 at 15:14, Gareth Aye <ga...@mozilla.com> wrote:

The integration tests have been working for me locally on node 0.12 for at least the past month (I'm on Ubuntu 14.04). Other people claim to be running into issues though?

On Wed, Jul 1, 2015 at 9:52 AM, Staś Małolepszy <st...@mozilla.com> wrote:

What's holding us back from upgrading to node 0.12? The default npm version for node 0.10 is 1.4, and if you want to have both 0.10 and 0.12 on your system, making 0.10 use npm 2.0 requires additional work.  It's not hard, but represents an additional step which might turn people away.

On Wed, Jul 1, 2015 at 3:46 PM, Tim Guan-tin Chien <timd...@mozilla.com> wrote:

On Wed, Jul 1, 2015 at 9:20 PM, Gareth Aye <ga...@mozilla.com> wrote:
> Would it work for you and others to lock down global dependencies for
> development to no...@0.10, npm@2, python@2.7, and virtualenv@13?

WFM if we explicitly fail when the versions don't match, thanks!

_______________________________________________
dev-gaia mailing list
dev-...@lists.mozilla.org

https://lists.mozilla.org/listinfo/dev-gaia

_______________________________________________
dev-gaia mailing list
dev-...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-gaia

[Gareth Aye]

If anyone really, really can't run the tests locally then I think :aus can help you get set up with a docker image that matches what we use on ci which we guarantee will work.

[Alberto Pastor]

Do I need to do something? I just run a test locally (in latests master) and had the same issue.

Do you want me to send you what I see in the console?

Thanks!

[Gareth Aye]

If you get latest master, remove your old node_modules, and then run make test-integration, you should be good to go. If not, it would help me to get your console output.

[Alberto Pastor]

http://pastebin.com/e4qHUNwR

[Gareth Aye]

Oh that's actually the same issue Ben is running into on osx. I am on Linux but borrowed a macbook from someone yesterday and couldn't reproduce that...

[Benjamin Francis]

On 8 July 2015 at 16:41, Alberto Pastor <apa...@mozilla.com> wrote:

http://pastebin.com/e4qHUNwR

Thank you for rescuing my sanity.

[Gareth Aye]

I'm pretty convinced this has to do with something unrelated in gaia's build system https://github.com/mozilla-b2g/gaia/blob/master/Makefile#L575, but Ben reported that turning that off didn't change anything for him? My $LANG (which is what python is checking for according to http://svn.python.org/projects/python/trunk/Lib/locale.py) is en_US.UTF-8...

[Augustin Trancart]

On 08/07/2015 16:51, Benjamin Francis wrote:

I'm just wondering, am I the only person who is having these problems, or are integration tests this unreliable for other people too?

With two identical PC on the same version of ubuntu, I have one that can run them, and one that cannot (tried everything from make clean, really clean, npm cache clean, reinstalling npm, reinstalling node, cloning gaia tree again) :-/

I didn't bug Gareth yet, because I need time to carefully compare those 2 environments to be extra-sure they are the same (and if not, where they differ). I'll give you a console.log as soon as I can Gareth.

Apart from that, I'm really interested in some Dockerfile/docker images for marionette! Are there any existing stuff I can pick somewhere?

Regards,

Augustin

[No-Jun Park]

Actually, I ran into this a while ago on my OSX, and turned it was because of the locale setting in mac os x. 

export LANG=POSIX

export LC_ALL=POSIX

 I did put above lines on console to resolve this issue at the time, but strangely, this didn’t reoccur to me afterwards.

No-Jun

On Jul 8, 2015, at 11:50 AM, Benjamin Francis <bfra...@mozilla.com> wrote:

On 8 July 2015 at 16:41, Alberto Pastor <apa...@mozilla.com> wrote:

http://pastebin.com/e4qHUNwR

Thank you for rescuing my sanity.

[robert...@gmail.com]

I managed to run the tests, but I can't make it log gecko messages.
I have a debug build for b2g-desktop and I ran the tests with VERBOSE=1, still nothing.
Any help?

Robert-

[Gareth Aye]

Do you want messages from content frames (stuff that gets written to the console api) or do you want gecko logs? You can apply https://github.com/mozilla-b2g/gaia/pull/30760 to get gecko logs. VERBOSE=1 pipes things from the console api to your marionette-js-runner proc.

On Wed, Jul 8, 2015 at 3:35 PM, <robert...@gmail.com> wrote:

miercuri, 1 iulie 2015, 01:46:55 UTC-7, Tim Guan-tin Chien a scris:

I managed to run the tests, but I can't make it log gecko messages.
I have a debug build for b2g-desktop and I ran the tests with VERBOSE=1, still nothing.
Any help?

Robert-

[Alberto Pastor]

Does DEBUG=1 help?

Regards!

robert...@gmail.com wrote:
> miercuri, 1 iulie 2015, 01:46:55 UTC-7, Tim Guan-tin Chien a scris:>> After repeating trial and error, I realized Gij only behaves if the

>> Tim> I managed to run the tests, but I can't make it log gecko messages.

> I have a debug build for b2g-desktop and I ran the tests with VERBOSE=1, still nothing.
> Any help?
>
> Robert-

--
Sent Using Firefox OS

[Benjamin Francis]

On 8 July 2015 at 19:03, No-Jun Park <np...@mozilla.com> wrote:

Actually, I ran into this a while ago on my OSX, and turned it was because of the locale setting in mac os x. 

export LANG=POSIX

export LC_ALL=POSIX

\o/ This worked for me on OS X! Thank you No-Jun for sharing, you are my hero.

Gareth, what's the right way to patch this in the Makefile?

Now just to figure out the timeout issues I'm having on Linux...

Ben

[Julien Wajsberg]

Le 09/07/2015 14:13, Benjamin Francis a écrit :

On 8 July 2015 at 19:03, No-Jun Park <np...@mozilla.com> wrote:

Actually, I ran into this a while ago on my OSX, and turned it was because of the locale setting in mac os x. 

export LANG=POSIX

export LC_ALL=POSIX

\o/ This worked for me on OS X! Thank you No-Jun for sharing, you are my hero.

Gareth, what's the right way to patch this in the Makefile?

I'd rather understand why issues happen with other locale settings...

Now just to figure out the timeout issues I'm having on Linux...

Ben

[Alexandre Lissy]

Le 09/07/2015 14:13, Benjamin Francis a écrit :
> On 8 July 2015 at 19:03, No-Jun Park <np...@mozilla.com

> <mailto:np...@mozilla.com>> wrote:
>
> Actually, I ran into this a while ago on my OSX, and turned it was
> because of the locale setting in mac os x.
>
> export LANG=POSIX
> export LC_ALL=POSIX
>
>
> \o/ This worked for me on OS X! Thank you No-Jun for sharing, you are my
> hero.
>
> Gareth, what's the right way to patch this in the Makefile?
>

> Now just to figure out the timeout issues I'm having on Linux...

And unit tests are back to completely broken on my system ... That was
working a few weeks ago ...

[No-Jun Park]

I just remembered some other things as well.  There were many complaints on web about being unable to run terminal apps in os x:

http://apple.stackexchange.com/questions/21096/where-does-lang-variable-gets-set-in-mac-os-x

http://blog.remibergsma.com/2012/07/10/setting-locales-correctly-on-mac-osx-terminal-application/

I think one thing I forgot to mention last time was that as mentioned in the 2nd link above, I also disabled the automatic setting of locale environment variable on startup (it was checked as default).  

I use iTerm, and it looks like this under the Terminal menu:

I think probably this is what caused the problem to go away.  I should have investigated further, but it didn’t bother me anymore so I moved on.  

No-Jun

On Jul 9, 2015, at 8:23 AM, Julien Wajsberg <jwaj...@mozilla.com> wrote:

Le 09/07/2015 14:13, Benjamin Francis a écrit :

On 8 July 2015 at 19:03, No-Jun Park <np...@mozilla.com> wrote:

Actually, I ran into this a while ago on my OSX, and turned it was because of the locale setting in mac os x. 

export LANG=POSIX

export LC_ALL=POSIX

\o/ This worked for me on OS X! Thank you No-Jun for sharing, you are my hero.

Gareth, what's the right way to patch this in the Makefile?

I'd rather understand why issues happen with other locale settings...

Now just to figure out the timeout issues I'm having on Linux...

Ben

[Alexandre Lissy]

So I ran into another of issues with being able to run Gaia Unit tests.

Symptom was:
- remove node_modules,
- try to reinstall it

Fails complaining it cannot find test-agent.

Fixed after deleting ~/.npm/test-agent/ and retrying.

Le 01/07/2015 10:46, Tim Guan-tin Chien a écrit :
> After repeating trial and error, I realized Gij only behaves if the
> following runtime has the exact version installed on your machine:
>
> node ~= 0.10
> npm ~= 2
> python ~= 2.7
> virtualenv ~= 13.1.0
>
> This is an unfriendly setup and require experience engineer to dive
> into the log to find out why, step-by-step. Particularly, the npm
> required is not the version preloaded with node v0.10.
>
> I have previously filed
> https://bugzilla.mozilla.org/show_bug.cgi?id=1170426 on this.
>
> Can we get a friendlier warning or error on this version requirements? Thanks.
>
>
> Tim

[Julien Wajsberg]

Let me complete what you say, because I was besides :)

Le 09/07/2015 18:01, Alexandre Lissy a écrit :
> So I ran into another of issues with being able to run Gaia Unit tests.
>
> Symptom was:
> - remove node_modules,
> - try to reinstall it
>
> Fails complaining it cannot find test-agent.

That's when we tried to run "npm install test-agent".
Even after deleting node_modules, we had this weird error when trying to
open a file in the "node_modules/test-agent" directory. What was weird
was that we didn't see any download happening.

>
> Fixed after deleting ~/.npm/test-agent/ and retrying.

"npm cache clean" is a standardized way to remove the cache in .npm. So
you may want to try this if nothing else worked yet.



Also, I don't know that's been said already, but node 0.12 doesn't work
for me lately. So you need node 0.10 and npm 2. I think we need to fix
this (filing a bug is a first step).

[augustin trancart]

Hi Gareth,

I still have the same errors. With

node: 0.10.25

npm: 2.12.0

python: 2.7.9

virtualenv: 12.1.1

node-gyp: 0.2.12

running make clean && make really-clean && npm cache clean then make test-integration fails with attached logs (make-test-integration.log).

Then i figured my solar system was not completely in syzygy, so I updated virtualenv to 13.1.0

running
make clean && make really-clean && npm cache clean

rm -rf ~/.node-gyp

make test-integration

produces the same error

then I thought a newer version of node-gyp could fix this (as the error seems to be related to gyp). I updated node-gyp to 2.0.1

same clean procedure

same make command

same error (see make-test-integration2.log and npm-debug.log)

Anyyway, I don't think it is version-related, because the exact same computer with the same ubuntu version with :

node 0.10.25

npm 2.11.2

node-gyp 0.12.2 (so the same as my first step)

python 2.7.9

virtualenv 13.0.3

works fine.

I don't think that it is a problem with my gaia tree either, because I did a fresh clone for these tests.

Planets seems to be aligned. Am I missing something or should I start to sacrifice kittens to increase my PC's karma? (I would rather not)

Please ask if more information is needed.

Thanks a lot,

Augustin

Augustin Trancart

Dev Engineer
+33 6 58 16 09 07

skype : augustin.trancart

[Julien Wajsberg]

I don't see the log because attachments are not sent to the mailing list. You should send them to a pastebin service :)

Here is a guess because you're talking about node-gyp: are you sure python does not default to python3 on your system ?
"python --version" should reply a python2 version.
If this is the case:

npm config set python python2

[augustin trancart]

Oh yes, I forgot that attachments don't go through, sorry for that (and thanks Julien for pointing this out):

first make test-integration output: https://pastebin.mozilla.org/8839149

2nd: https://pastebin.mozilla.org/8839148

npm-debug.log: https://pastebin.mozilla.org/8839150

python --version replies 2.7.9 :-/

Augustin Trancart

Dev Engineer
+33 6 58 16 09 07

skype : augustin.trancart

[Gareth Aye]

So it seems like you're using aversion of gyp that's incompatible with the node-gyp we're using in gaia. This is kind of strange since node-gyp bundles gyp. Is it possible you previously had gyp globally installed? If so, uninstalling the global gyp should fix the problem.

[Augustin Trancart]

It's working \o/ Thanks Gareth, you've given me a good hint :-)

What I did:
- run the script from here https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager to make sure I have the right repo.
Apparently I've installed directly from my package manager before.
- then
sudo apt-get dist-upgrade
sudo apt-get autoremove
This has removed nodejs (that only tells me there's something wrong, nodejs should have been marked as manually installed), npm, node-gyp, gyp and everything node related actually.
sudo apt-get install nodejs // that also install rlwrap, but not gyp by default.
(and sudo ln -s /usr/bin/nodejs /usr/bin/node)

Then

make clean && make really-clean && npm cache clean

make test-integration // works ok now \o/

What is really odd is that I didn't use the joyent script on my other pc, and I have no problem whatsoever.

Regards,

Augustin Trancart
Phoxygen

[Julien Wajsberg]

Usually I really advise against using the joyent script. But if it works for you it's fine I guess !

[Alexandre Lissy]

So I am also spotting issues on test infra:
https://s3-us-west-2.amazonaws.com/taskcluster-public-artifacts/83c5GU8UQFqzSeqpv-5Emg/0/public/logs/live_backing.log

At the end of this log, there is this error, but I don't know what
exactly it means:

----------------------------------------------------------------------
11:49:44 INFO - npm ERR! Linux 3.13.0-48-generic
11:49:44 INFO - npm ERR! argv "node" "/usr/local/bin/npm" "run"
"marionette" "--" "--buildapp=desktop" "--reporter=mocha-tbpl-reporter"
11:49:44 INFO - npm ERR! node v0.10.36
11:49:44 INFO - npm ERR! npm v2.11.0
11:49:44 INFO - npm ERR! code ELIFECYCLE
11:49:44 INFO - npm ERR! ga...@0.0.3 marionette: `gaia-marionette
"--buildapp=desktop" "--reporter=mocha-tbpl-reporter"`
11:49:44 INFO - npm ERR! Exit status 1
11:49:44 INFO - npm ERR!
11:49:44 INFO - npm ERR! Failed at the ga...@0.0.3 marionette script
'gaia-marionette "--buildapp=desktop" "--reporter=mocha-tbpl-reporter"'.
11:49:44 INFO - npm ERR! This is most likely a problem with the
gaia package,
11:49:44 INFO - npm ERR! not with npm itself.
11:49:44 INFO - npm ERR! Tell the author that this fails on your
system:
11:49:44 INFO - npm ERR! gaia-marionette "--buildapp=desktop"
"--reporter=mocha-tbpl-reporter"
11:49:44 INFO - npm ERR! You can get their info via:
11:49:44 INFO - npm ERR! npm owner ls gaia
11:49:44 INFO - npm ERR! There is likely additional logging output
above.
11:49:44 INFO - npm ERR! Please include the following file with any
support request:
11:49:44 INFO - npm ERR! /home/worker/gaia/npm-debug.log
11:49:44 INFO - make: *** [test-integration-test] Error 1
----------------------------------------------------------------------

Is that just harness failure or is npm getting into some weird state?

Le 01/07/2015 10:46, Tim Guan-tin Chien a écrit :
> After repeating trial and error, I realized Gij only behaves if the
> following runtime has the exact version installed on your machine:
>
> node ~= 0.10
> npm ~= 2
> python ~= 2.7
> virtualenv ~= 13.1.0
>
> This is an unfriendly setup and require experience engineer to dive
> into the log to find out why, step-by-step. Particularly, the npm
> required is not the version preloaded with node v0.10.
>
> I have previously filed
> https://bugzilla.mozilla.org/show_bug.cgi?id=1170426 on this.
>
> Can we get a friendlier warning or error on this version requirements? Thanks.
>
>
> Tim

[Gareth Aye]

Is that on master?

[Alexandre Lissy]

Le 25/07/2015 14:09, Gareth Aye a écrit :
> Is that on master?

yes, sorry, I forgot the other link:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=81480b83ce3e

> > dev-...@lists.mozilla.org <mailto:dev-...@lists.mozilla.org>

> > https://lists.mozilla.org/listinfo/dev-gaia
> >
>
> _______________________________________________
> dev-gaia mailing list

> dev-...@lists.mozilla.org <mailto:dev-...@lists.mozilla.org>
> https://lists.mozilla.org/listinfo/dev-gaia
>
>

[Alexandre Lissy]

Le 25/07/2015 14:19, Alexandre Lissy a écrit :
> Le 25/07/2015 14:09, Gareth Aye a écrit :
>> Is that on master?
>
> yes, sorry, I forgot the other link:
> https://treeherder.mozilla.org/#/jobs?repo=try&revision=81480b83ce3e

There are other instances ...

Here, at least one in one failure of Gij 22:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=56005b949dab

https://s3-us-west-2.amazonaws.com/taskcluster-public-artifacts/Da-6cbftSgWkrudkklARgg/0/public/logs/live_backing.log

10:55:39 INFO - [marionette-mocha] Error: invalid interface
"/home/worker/gaia/node_modules/marionette-js-runner/lib/ui"
10:55:39 INFO - at Mocha.ui
(/home/worker/gaia/node_modules/mocha/lib/mocha.js:154:24)
10:55:39 INFO - at Object.<anonymous>
(/home/worker/gaia/node_modules/mocha/bin/_mocha:195:7)
10:55:39 INFO - at Module._compile (module.js:456:26)
10:55:39 INFO - at Object.Module._extensions..js (module.js:474:10)
10:55:39 INFO - at Module.load (module.js:356:32)
10:55:39 INFO - at Function.Module._load (module.js:312:12)
10:55:39 INFO - at Function.Module.runMain (module.js:497:10)
10:55:39 INFO - at startup (node.js:119:16)
10:55:39 INFO - at node.js:929:3