SpaceJam and 2.4.5_6 Hangs, or returns no output.

[Pushplaybang]

Having some weird issues with little visibility into whats causing them.

Summary

• the web reporter seems be running fine.
• specifying the console reporter returns nothing to the console.
• using it with practiclemeteor:console-test-runner causes it to hang.

I've tried to explain my specific issues and the circumstances of them below, please let me know what other information I can provide.

Here are the top level packages I'm using for testing:

practicalmeteor:mocha@2.4.5_5
practicalmeteor:mocha-console-runner@0.2.3
practicalmeteor:chai@2.1.0_1
practicalmeteor:sinon@1.14.1_2
lmieulet:meteor-coverage           
xolvio:cleaner                     
xolvio:backdoor                    
dburles:factory                    
hwillson:stub-collections          
tmeasday:acceptance-test-driver

I have the latest spacejam, phantom-prebuilt and chimp installed globally

my test commands for CI look like this:

# unit
"test:ci": "cd app/ && spacejam test --settings settings/settings-test.json --driver-package practicalmeteor:mocha-console-runner",

# integration
"test:ci-app": "cd app/ && spacejam test --full-app --once --settings settings/settings-test.json --driver-package practicalmeteor:mocha-console-runner",

# acceptance tests with chimp and mocha are not affected

• All of this works almost as expected with `2.4.5_5 with the smallest of issues. Though i beginning to feel like this entire setup is a bit fragile am I doing something wrong?

2.4.5_6 with spacejam

2.4.5_5 Causes tests with spacejam and the console-reporter to hang with no clear error message.

No output with new console reporter

I assumed I would be able to practlemeteor:mocha with the console reporter added in 2.4.5_5 which seems to run the tests, but provide no test output, only the spacejam startup and shut down.

Problems with 2.4.5_5

the only real problem with 2.4.5_5 is the regular STDERR console output inbetween the tests, that just shouldn't be there but doesn't actually effect the running of the tests, other than the console readability.

Thank you for all of the great work on these packages so far, testing is vital to Meteor maturing as a framework, and I'd love to see all of this become more standardized and simpler to start off with.