-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guard::Spork failed to achieve its <start>, exception was ... #107
Comments
The same issue here on Ubuntu 12.10. |
Ok, have you already open an issue on childprocess? |
Hi Thibaud, No, i didn't. Will you do it? Maybe you can describe more precisely than me ;) . cheers |
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. |
Mogria's solution removed the exception. Cheers, seems to be an error with childprocess 0.3.7 |
Same as darokel |
ChildProcess change how we need to build process because of enkessler/childprocess#46 - #107
Can you try guard-spork from master branch to see if it's fixed? Thanks! |
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 : ) |
@RaimundSchramm with |
Hi Thibaud, No, at first i just did a normal bundle update guard-spork with I just tried cheers |
I should be ok, I'll release 1.4.2 when rubygems will be back! |
1.4.2 released! |
I'm new to programming. Can someone help explain to me how to downgrade ChildProcess? |
replace your current line in the
|
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 Gems used only for assets and not requiredin production environments by default.group :assets do gem 'jquery-rails', '2.0.2' Test gems on Macintosh OS Xgroup :test do group :production do |
then simply add the line to the gemfile and then run |
That did it! Thank you! |
Apparently this isn't fixed yet since I ran into it today. Thank's for solving the problem for me. |
@jeff-romine are you using the last version of |
Adding |
same problem today, so I tried to downgrade to 0.3.6 and this is what I got: The bundle currently has childprocess locked at 0.3.9. |
I also have caught this issue,how to downgrade the version from 0.3.9 to 0.3.6? |
@ThreeStar Add |
@thibaudgg Thanks,guy~ It works. |
Thanks! This was helpful. I followed the comments from @thibaudgg: Add |
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 |
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:
So i tried downgrading childprocess to 0.3.6 and it seems to work for me right now.
Have a nice weekend.
Raimund
The text was updated successfully, but these errors were encountered: