guard / guard-spork

Guard::Spork automatically manage Spork DRb servers
https://rubygems.org/gems/guard-spork
MIT License
296 stars 58 forks source link

Guard::Spork failed to achieve its <start>, exception was ... #107

Closed RaimundSchramm closed 11 years ago

RaimundSchramm commented 11 years ago

Hi there,

i am not sure if it is an issue and if it is i don't know to wich technology it belongs. So maybe this is of some help otherwise sorry for posting and delete.

Today i wanted to speed up my Integration testing as recommanded with Capybara and Poltergeist using PhantomJs. I already had a setup test suite in place with a usual technology stack like guard-spork, spork-rails, rspec-rails, jasminrice, capybara, factory_girl_rails and dependencies. All is setup as usual on up to date Ubuntu 12.04, with all needed system libraries, rvm, ruby 1.9.3 and rails 3.2.x.

Executing 'bundle exec guard' throws:

System:~/appdir$ bundle exec guard 11:38:29 - INFO - Guard uses Libnotify to send notifications. 11:38:29 - INFO - Guard uses TerminalTitle to send notifications. 11:38:29 - INFO - Guard is now watching at '/appdir' 11:38:29 - INFO - LiveReload 1.6 is waiting for a browser to connect. 11:38:29 - INFO - Starting Spork for RSpec 11:38:30 - ERROR - Guard::Spork failed to achieve its , exception was:

[#5730B1D20317] ChildProcess::LaunchError: No such file or directory - bundle exec spork -p 8989 [#5730B1D20317] /gemsetdir/childprocess-0.3.7/lib/childprocess/unix/fork_exec_process.rb:54:in launch_process' [#5730B1D20317] /gemsetdir/childprocess-0.3.7/lib/childprocess/abstract_process.rb:68:instart' [#5730B1D20317] /gemsetdir/guard-spork-1.2.3/lib/guard/spork/spork_instance.rb:40:in start' [#5730B1D20317] /gemsetdir/guard-spork-1.2.3/lib/guard/spork/runner.rb:33:ineach' [#5730B1D20317] /gemsetdir/guard-spork-1.2.3/lib/guard/spork/runner.rb:33:in launch_sporks' [#5730B1D20317] /gemsetdir/guard-spork-1.2.3/lib/guard/spork.rb:22:instart' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard/runner.rb:99:in block in run_supervised_task' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard/runner.rb:97:incatch' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard/runner.rb:97:in run_supervised_task' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard/runner.rb:54:inblock (2 levels) in run' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard/runner.rb:170:in block (3 levels) in scoped_guards' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard/runner.rb:169:ineach' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard/runner.rb:169:in block (2 levels) in scoped_guards' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard/runner.rb:168:incatch' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard/runner.rb:168:in block in scoped_guards' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard/runner.rb:167:ineach' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard/runner.rb:167:in scoped_guards' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard/runner.rb:53:inblock in run' [#5730B1D20317] /gemsetdir/lumberjack-1.0.2/lib/lumberjack.rb:27:in unit_of_work' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard/runner.rb:52:inrun' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard.rb:162:in block in start' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard.rb:334:inblock in within_preserved_state' [#5730B1D20317] internal:prelude:10:in synchronize' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard.rb:331:inwithin_preserved_state' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard.rb:161:in start' [#5730B1D20317] /gemsetdir/guard-1.5.4/lib/guard/cli.rb:104:instart' [#5730B1D20317] /gemsetdir/thor-0.16.0/lib/thor/task.rb:27:in run' [#5730B1D20317] /gemsetdir/thor-0.16.0/lib/thor/invocation.rb:120:ininvoke_task' [#5730B1D20317] /gemsetdir/thor-0.16.0/lib/thor.rb:275:in dispatch' [#5730B1D20317] /gemsetdir/thor-0.16.0/lib/thor/base.rb:425:instart' [#5730B1D20317] /gemsetdir/guard-1.5.4/bin/guard:6:in <top (required)>' [#5730B1D20317] /gemset/bin/guard:23:inload' [#5730B1D20317] /gemset/bin/guard:23:in `

'

So i tried downgrading childprocess to 0.3.6 and it seems to work for me right now.

Have a nice weekend. Raimund

mogria commented 11 years ago

The same issue here on Ubuntu 12.10. Downgrading to childprocess 0.3.6 worked for me too

thibaudgg commented 11 years ago

Ok, have you already open an issue on childprocess?

RaimundSchramm commented 11 years ago

Hi Thibaud,

No, i didn't. Will you do it? Maybe you can describe more precisely than me ;) .

cheers

darokel commented 11 years ago

Hi, getting this same error on OSX. Weird, I have another app with the same test stack and that loads up fine but on my new app, I get this exception.

darokel commented 11 years ago

Mogria's solution removed the exception. Cheers, seems to be an error with childprocess 0.3.7

buholoco commented 11 years ago

Same as darokel Mogria's solution (downgraded childprocess to 0.3.6) removed the exception. Cheers, seems to be an error with childprocess 0.3.7

thibaudgg commented 11 years ago

Can you try guard-spork from master branch to see if it's fixed? Thanks!

RaimundSchramm commented 11 years ago

Hi,

so i did upgrade only childprocess to verify the error is still there. Then i did bundle update for guard-spork only which updated it and all dependencies (not sure if that was what you meant).

With the most recent gems in place the error is gone.

Thx for the effort : )

thibaudgg commented 11 years ago

@RaimundSchramm with gem 'guard-spork', github: 'guard/guard-spork' in your Gemfile right? (just to be sure)

RaimundSchramm commented 11 years ago

Hi Thibaud,

No, at first i just did a normal bundle update guard-spork with gem 'guard-spork' which installed version 1.4.1.

I just tried gem 'guard-spork', github: 'guard/guard-spork' as you asked and it works as well. (Is it enough to update the entries in the Gemfile and bundle install or do i have to do something else?)

cheers

thibaudgg commented 11 years ago

I should be ok, I'll release 1.4.2 when rubygems will be back!

thibaudgg commented 11 years ago

1.4.2 released!

CoolJorcz commented 11 years ago

I'm new to programming. Can someone help explain to me how to downgrade ChildProcess?

mogria commented 11 years ago

replace your current line in the Gemfile which installs the child process gem with the following one

gem 'childprocess', '0.3.6'
CoolJorcz commented 11 years ago

Hi Mogria,

My GemFile doesn't have ChildProcess. Would it be included in another gem? Here are the contents:

gem 'rails', '3.2.12'

group :development, :test do gem 'sqlite3', '1.3.5' gem 'rspec-rails', '2.11.0' gem 'guard-rspec', '1.2.1' gem 'guard-spork', '1.2.0' gem 'spork', '0.9.2' end

Gems used only for assets and not required

in production environments by default.

group :assets do gem 'sass-rails', '3.2.5' gem 'coffee-rails', '3.2.2' gem 'uglifier', '1.2.3' end

gem 'jquery-rails', '2.0.2'

Test gems on Macintosh OS X

group :test do gem 'capybara', '1.1.2' gem 'rb-fsevent', '0.9.1', :require => false gem 'growl', '1.0.3' end

group :production do gem 'pg', '0.12.2' end

mogria commented 11 years ago

then simply add the line to the gemfile

and then run bundle install again

CoolJorcz commented 11 years ago

That did it! Thank you!

jeff-romine commented 11 years ago

Apparently this isn't fixed yet since I ran into it today. Thank's for solving the problem for me.

thibaudgg commented 11 years ago

@jeff-romine are you using the last version of guard, guard-spork, spork and bundle exec ...? Please also read the https://github.com/guard/guard/blob/master/CONTRIBUTING.md guide to be sure to give all useful info. Thanks

meowsus commented 11 years ago

Adding gem "childprocess", "0.3.6" to my Gemfile worked for me!

stellorior commented 11 years ago

same problem today, so I tried to downgrade to 0.3.6 and this is what I got: You have requested: childprocess = 0.3.6

The bundle currently has childprocess locked at 0.3.9. Try running bundle update childprocess --> I did "bundle update childprocess" and now it seems to work fine.

ThreeStar commented 11 years ago

I also have caught this issue,how to downgrade the version from 0.3.9 to 0.3.6?

thibaudgg commented 11 years ago

@ThreeStar Add gem 'childprocess', '0.3.6' to your Gemfile and run bundle update childprocess

ThreeStar commented 11 years ago

@thibaudgg Thanks,guy~ It works.

trentscott2 commented 11 years ago

Thanks! This was helpful. I followed the comments from @thibaudgg:

Add gem 'childprocess', '0.3.6' to your Gemfile and run bundle update childprocess.

shuke0327 commented 11 years ago

I meet the same problem, and fixed it by upgrade gem "guard-spork" from 1.2.0 to 1.4.2, and it works well.

the childprocess gem version is 0.3.9