"Timeout waiting for the Jasmine test results!" when specs run fine

[drewB]

I am running with jasminerice. When I run guard I am getting:

13:11:44 - ERROR - An error occurred: Timeout waiting for the Jasmine test results!
> [#C35FBACA4DD3] 
> [#C35FBACA4DD3] Jasmine 1.2.0 revision 1337005947
> [#C35FBACA4DD3] Running 476 of 708 specs

Followed by a bunch of spec listings. If I pull up the URL in my browser all 708 specs run in about 9 secs without any failures. I have the server_timeout set to 120.

guard :jasmine, :port => 8888, :jasmine_url => 'http://127.0.0.1:8888/jasmine', :server_timeout => 120 do

[drewB]

Just discovered that you can pass a spec runner timeout value in guard-jasmine. Setting that to 30 seconds did the job. Looking for a way to do that in the guard file.

[drewB]

Added :timeout => 30 to my guardfile and that did the job. I was thrown by the server_timeout being different.

guard :jasmine, :port => 8888, :jasmine_url => 'http://127.0.0.1:8888/jasmine', :server_timeout => 120, :timeout => 30 do

[nicosantangelo]

I'm having the same problem but using the jasmine gem (Jasmine 2.0.0) in a Rails project. If I go to the URL in Chrome all specs run fine, but guard throws:

 An error occurred: Timeout waiting for the Jasmine test results!
> [#407BCA032AF4]
> [#407BCA032AF4] Jasmine2.0.0finished in 3.716s
> [#407BCA032AF4] raise exceptions 
> [#407BCA032AF4] 300 specs, 0 failures

followed by every spec message.

Guardfile:

guard 'jasmine', server: :jasmine_gem, port: 8888, jasmine_url: 'http://localhost:8888/', timeout: 120, server_timeout: 120 do

Gemfile.lock

  guard (2.3.0)
  guard-jasmine (1.19.0)
  jasmine (2.0.0)
  jasmine-core (2.0.0)

I tried running only one spec and changing the timeouts but with no luck.

Everything worked fine until I upgraded jasmine to 2.0.0, I don't know if I missed something but I can't get it to work again.

Thanks a lot and sorry if I'm posting this on the wrong place.

[brendonrapp]

I am having the same problem as @nicosantangelo. I ended up here while looking for a solution.

[brendonrapp]

Opened new issue, #161, for the problem @nicosantangelo and I are experiencing.