search

netzpirat / guard-cucumber

Guard::Cucumber automatically runs your features (much like autotest)
https://rubygems.org/gems/guard-cucumber
MIT License
39 stars 56 forks source link

Guard fails when using rvm 1.9.3 #28

Closed DVG closed 12 years ago

DVG commented 12 years ago

It appears to be trying to register with growl for notifications, but it's failing

OSERROR: -10000 MESSAGE: Apple event handler failed. COMMAND: app("/Users/DVG/Library/PreferencePanes/Growl.prefPane/Contents/Resources/GrowlHelperApp.app").register({:all_notifications=>["success", "pending", "failed", "notify"], :as_application=>"Guard", :default_notifications=>"notify"}) from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/rb-appscript-0.6.1/lib/appscript.rb:642:in method_missing' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/growl_notify-0.0.3/lib/growl_notify.rb:29:inregister' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/growl_notify-0.0.3/lib/growl_notify.rb:19:in config' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/guard-0.9.1/lib/guard/notifiers/growl_notify.rb:42:inavailable?' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/guard-0.9.1/lib/guard/notifier.rb:109:in add_notification' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/guard-0.9.1/lib/guard/notifier.rb:146:inblock in auto_detect_notification' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/guard-0.9.1/lib/guard/notifier.rb:146:in each' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/guard-0.9.1/lib/guard/notifier.rb:146:inany?' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/guard-0.9.1/lib/guard/notifier.rb:146:in auto_detect_notification' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/guard-0.9.1/lib/guard/notifier.rb:72:inturn_on' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/guard-0.9.1/lib/guard.rb:167:in start' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/guard-0.9.1/lib/guard/cli.rb:74:instart' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/thor-0.14.6/lib/thor/task.rb:22:in run' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/thor-0.14.6/lib/thor/invocation.rb:118:ininvoke_task' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/thor-0.14.6/lib/thor.rb:263:in dispatch' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/thor-0.14.6/lib/thor/base.rb:389:instart' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/gems/guard-0.9.1/bin/guard:6:in <top (required)>' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/bin/guard:19:inload' from /Users/DVG/.rvm/gems/ruby-1.9.3-p0/bin/guard:19:in `

'

I switched over to the system default 1.8.7, and it at least got farther, but then my config files didn't work because of 1.9.3 style syntax

netzpirat commented 12 years ago

Can you try to use ruby_gntp? Scott Davis (the author of growl_notify) discourages the use of growl_notify and uses ruby_gntp now, since there were too many problems with rb-appscript.

DVG commented 12 years ago

I'll give that a shot and report back

DVG commented 12 years ago

That seemed to clear up the error, but it's not running the cukes whenever I make a change to the features or step definitions like I'd expect. Any suggestions on what to try?

After the first run on starting up guard, I get

Running all features Disabling profiles... .........

2 scenarios (2 passed) 9 steps (9 passed) 0m0.572s

I can type in cucumber to run it again, but it doesn't run automatically.

netzpirat commented 12 years ago

Does the watcher match your project structure? What's your OS and Ruby version?

DVG commented 12 years ago

Using OS X Lion, RVM 1.9.3 Ruby

The default watcher appears to match my project structure. I'm using the Rails default features directory with features named things like "dashboard.feature"

netzpirat commented 12 years ago

And when you manually touch a feature, nothing happens at all? Can you place a debug statement at https://github.com/netzpirat/guard-cucumber/blob/master/lib/guard/cucumber.rb#L83 to see if Guard triggers guard-cucumber at all? Perhaps this is a problem with rb-fsevent or Guard.

netzpirat commented 12 years ago

Closing this, since I got no feedback. You can reopen it again if it is still an issue.