Weird log message when test fails

[mpaulucci]

Hi, I'm trying to make Testacular(0.4.0) work with my existing AngularJS application.

When I run a sample test that passes, when I run yeoman test I get the correct output:

Running "test" task
info: Testacular server started at http://localhost:8080/
info (launcher): Starting browser PhantomJS
info (PhantomJS 1.7): Connected on socket id -1WsgJQW786BjanD5-kq
PhantomJS 1.7: Executed 1 of 1 SUCCESS (0.295 secs / 0.039 secs)
info: Disconnecting all browsers
Done, without errors.

But when I change the test to fail, I get this huge warning message after the error output:

Command failed: JOIN 5 / /usr/lib/node_modules/testacular/adapter/lib/jasmine.js
JOIN 6 / /usr/lib/node_modules/testacular/adapter/lib/jasmine.js
JOIN 5 / /usr/lib/node_modules/testacular/adapter/jasmine.js
JOIN 6 / /usr/lib/node_modules/testacular/adapter/jasmine.js
JOIN 5 / /home/martin/workspace/qa-tool/client/app/scripts/vendor/jquery-1.9.0.js
JOIN 6 / /home/martin/workspace/qa-tool/client/app/scripts/vendor/jquery-1.9.0.js
JOIN 5 / /home/martin/workspace/qa-tool/client/app/scripts/vendor/jquery-ui-1.10.0.js
JOIN 6 / /home/martin/workspace/qa-tool/client/app/scripts/vendor/jquery-ui-1.10.0.js
JOIN 5 / /home/martin/workspace/qa-tool/client/app/scripts/vendor/bootstrap.js
JOIN 6 / /home/martin/workspace/qa-tool/client/app/scripts/vendor/bootstrap.js
JOIN 5 / /home/martin/workspace/qa-tool/client/app/scripts/vendor/angular.js
JOIN 6 / /home/martin/workspace/qa-tool/client/app/scripts/vendor/angular.js
JOIN 5 / /home/martin/workspace/qa-tool/client/app/scripts/vendor/angular-resource.js
JOIN 6 / /home/martin/workspace/qa-tool/client/app/scripts/vendor/angular-resource.js
JOIN 5 / /home/martin/workspace/qa-tool/client/app/scripts/vendor/angular-ui.js
JOIN 6 / /home/martin/workspace/qa-tool/client/app/scripts/vendor/angular-ui.js
... etc.
Use --force to continue.

Is this a bug? How can I get rid of it?

[kimjoar]

This appears to have been introduced in isaacs/node-glob@9b4155a

[vojtajina]

Yep, sounds like problem in glob. This is fixed in canary, as we set fixed deps and will update to latest glob once the issue gets fixed.

Can you try install older glob ?

cd <path-to-testacular>
npm install glob@3.1.14

[vojtajina]

Please re-open the issue, if this does not fix it.

[vojtajina]

Ok it looks like fixed glob has been released, so can you try it with the latest instead ?

npm install glob@3.1.19

[kimjoar]

It was fixed in 3.1.20, not 3.1.19 :)

npm install glob@3.1.20

[vojtajina]

Thanks @kjbekkelund

[mpaulucci]

With glob 3.1.20 it works like a charm =)

[vojtajina]

Glad to hear that. I updated the deps to use glob 3.1.20 https://github.com/testacular/testacular/commit/e34d8834d69ec4e022fcd6e1be4055add96d693c