PhantomJS timeout with requirejs target, even on most basic config about grunt-contrib-jasmine HOT 5 CLOSED

This is due to two things, a missing slash at the end of the host option so the url generated is malformed and the connect task in npm not seeming to respect custom port config. The npm version isn't up to date with the repo so this is likely fixed.

In order to get you further, change your host line to

host: 'http://127.0.0.1:<%= connect.port %>/',

And set the port to 8000 in connect until that gets updated.

I'll add some protection against malformed urls, thanks for the heads up.

from grunt-contrib-jasmine.

I was actually already running the current head of grunt-contrib-connect. Adding the trailing slash does appear to have changed something, but it hasn't fixed it. Previously, the task would fail with the timeout error. Now it just hangs indefinitely.

from grunt-contrib-jasmine.

Can you run your tests via grunt connect jasmine -vd and post your output? (substitute your multitask directives if necessary)

I am trying to replicate your issue and I can't with the gist you provided, the trailing slash added, and grunt-contrib-connect running from head (with custom ports supported).

from grunt-contrib-jasmine.

D....oh.

So there were, by my count, 4 errors with what I was trying to do. Youch. There were the two you pointed out. Then

3. I was trying to run the jasmine task without also running connect.
4. I was trying to set the connect port inside the options hash instead of at the root of the task settings. Running in verbose tipped me off to that.

Thanks so much for your help! Sorry to waste your time - especially on a weekend.

from grunt-contrib-jasmine.

No problem, glad it worked out and thanks for highlighting some documentation failures. I'll take care of that soon.

from grunt-contrib-jasmine.