Client and server port don't agree?

[mathie]

I guess this is related to the changes for #89? Running guard-jasmine through guard, I'm now getting:

16:52:06 - INFO - Guard::Jasmine starts thin test server on port 59534 in development environment.
16:52:13 - INFO - Waiting for Jasmine test runner at http://localhost:8888/jasmine
16:52:13 - ERROR - Jasmine test runner isn't available: Connection refused - connect(2)

Dropping back to 1.9.4 gets me back to working again.

[netzpirat]

Did you use the :jasmine_url in your Guardfile?

[mathie]

Nope. I've just verified and it's still the stock Guardfile block generated by bundle exec guard init jasmine.

[pibako]

I have got exactly the same issue and I have nothing fancy in my Guardfile.

notification :off

guard :test do
  watch(%r{^lib/(.+)\.rb$})     { |m| "test/#{m[1]}_test.rb" }
  watch(%r{^test/.+_test\.rb$})
  watch('test/test_helper.rb')  { "test" }

  # Rails example
  watch(%r{^app/models/(.+)\.rb$})                   { |m| "test/unit/#{m[1]}_test.rb" }
  watch(%r{^app/controllers/(.+)\.rb$})              { |m| "test/functional/#{m[1]}_test.rb" }
  watch(%r{^app/views/.+\.rb$})                      { "test/integration" }
  watch('app/controllers/application_controller.rb') { ["test/functional", "test/integration"] }
end

guard :jasmine, :server_timeout => 30 do
  watch(%r{spec/javascripts/spec\.(js\.coffee|js|coffee)$}) { 'spec/javascripts' }
  watch(%r{spec/javascripts/.+_spec\.(js\.coffee|js|coffee)$})
  watch(%r{app/assets/javascripts/(.+?)\.(js\.coffee|js|coffee)(?:\.\w+)*$}) { |m| "spec/javascripts/#{ m[1] }_spec.#{ m[2] }" }
end

[netzpirat]

Thanks for the feedback. I can confirm the issue and will release a fix today.

[netzpirat]

Thanks a lot for reporting. I really did not notice that #89 was implemented half-assed, because I have set :jasmine_url in my current project. Fixed in 1.10.1.

[pibako]

Upgrading to the new version has removed quite many dependencies. This is the error I got when running 1.10.1:

Guard::Jasmine failed to achieve its <start>, exception was:
> [#4EB8A2D9DD74] LoadError: cannot load such file -- childprocess
...

[netzpirat]

That's very strange! I did not change anything in the projects gem spec and the childprocess gem is declared as dependency, which is also visible at the RubyGems page. But still, I also get the same error when using guard-jasmine from Rubygems, but not when running local as bundled dependency.

[netzpirat]

Looks like Rubygems had a hiccup. After running bundle update again, childprocess was bundled correctly and it works fine now.

[pibako]

It works now, thx!

[mathie]

Awesome, thank you!

G

On 22 Nov 2012, at 20:28, Piotr Kowalski [email protected] wrote:

It works now, thx!

—
Reply to this email directly or view it on GitHub.

Graeme Mathieson

Follow me on Twitter: http://twitter.com/mathie
Blog: http://woss.name/
Telephone: +44 (0)7949 0777 44