growl not working with rspec, but it does for other things

[jjb]

I get growl notifications for guard starting up, starting and stoping rails, etc. But I don't get notifications when specs pass and fail.

guard (2.1.0)

guard-rspec (4.0.1)

growl (1.0.3)

let me know if you want more info

[thibaudgg]

Could you share your Guardfile and Gemfile please? You can also try with ruby_gntp gem instead of growl.

[jjb]

okay, i sent you the files

In case it's relevant, I get this message whenever running specs:

WARN: Unresolved specs during Gem::Specification.reset:
      rspec-mocks (~> 2.14.0)
      rb-inotify (>= 0.9)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
Run options: include {:focus=>true}

[thibaudgg]

Try to run gem cleanup to remove this warning. Have you try with ruby_gntp instead of growl gem?
Please try also to run guard in debug mode with --debug and paste the output here. Thanks!

[jjb]

Have you try with ruby_gntp instead of growl gem?

yes, same behavior

try also to run guard in debug mode with --debug and paste the output here

➔ guard --debug
13:58:52 - DEBUG - Command execution: growlnotify --version
13:58:52 - DEBUG - Command execution: emacsclient --eval '1' 2> /dev/null || echo 'N/A'
13:58:52 - INFO - Guard is using Growl to send notifications.
13:58:52 - INFO - Guard is using TerminalTitle to send notifications.
13:58:52 - DEBUG - Command execution: hash stty
13:58:52 - DEBUG - Guard starts all plugins
13:58:52 - DEBUG - Hook :start_begin executed for Guard::RSpec
13:58:52 - INFO - Guard::RSpec is running
13:58:52 - DEBUG - Hook :start_end executed for Guard::RSpec
13:58:52 - DEBUG - Hook :start_begin executed for Guard::Rails
13:58:52 - INFO - [Guard::Rails] will start the default web server on port 3000 in development.
13:58:52 - INFO - Starting Rails...

13:58:52 - DEBUG - Command execution: {"RAILS_ENV"=>"development"} sh -c 'cd "/Users/john/appname" && rails server   -e development --pid "/Users/john/appname/tmp/pids/development.pid" -p 3000  &'
=> Booting Puma
=> Rails 4.0.0 application starting in development on http://0.0.0.0:3000
=> Run `rails server -h` for more startup options
=> Ctrl-C to shutdown server
Puma 2.6.0 starting...
* Min threads: 0, max threads: 16
* Environment: development
* Listening on tcp://0.0.0.0:3000
13:58:58 - INFO - Rails started, pid 36218

13:58:58 - DEBUG - Hook :start_end executed for Guard::Rails
13:58:58 - DEBUG - Hook :start_begin executed for Guard::LiveReload
13:58:58 - DEBUG - Hook :start_end executed for Guard::LiveReload
13:58:58 - INFO - Guard is now watching at '/Users/john/appname'
13:58:58 - INFO - LiveReload is waiting for a browser to connect.
13:58:58 - DEBUG - Command execution: stty -g 2>/dev/null
13:58:58 - DEBUG - Start interactor
13:59:03 - DEBUG - Stop interactor
13:59:03 - DEBUG - Command execution: stty gfmt1:cflag=4b00:iflag=6b02:lflag=200005cb:oflag=3:discard=f:dsusp=19:eof=4:eol=ff:eol2=ff:erase=7f:intr=3:kill=15:lnext=16:min=1:quit=1c:reprint=12:start=11:status=14:stop=13:susp=1a:time=0:werase=17:ispeed=9600:ospeed=9600 2>/dev/null 
13:59:03 - DEBUG - Command execution: stty -g 2>/dev/null
13:59:03 - DEBUG - Start interactor
13:59:08 - DEBUG - Stop interactor
13:59:08 - DEBUG - Command execution: stty gfmt1:cflag=4b00:iflag=6b02:lflag=200005cb:oflag=3:discard=f:dsusp=19:eof=4:eol=ff:eol2=ff:erase=7f:intr=3:kill=15:lnext=16:min=1:quit=1c:reprint=12:start=11:status=14:stop=13:susp=1a:time=0:werase=17:ispeed=9600:ospeed=9600 2>/dev/null 
13:59:08 - DEBUG - Hook :run_on_modifications_begin executed for Guard::RSpec
13:59:08 - INFO - Running: spec/controllers/foos_controller_spec.rb
Run options: include {:focus=>true}

All examples were filtered out; ignoring {:focus=>true}

FoosController
[... output of passing specs...]

Finished in 0.46682 seconds
16 examples, 0 failures

Randomized with seed 41284

13:59:13 - DEBUG - Hook :run_on_modifications_end executed for Guard::RSpec
13:59:13 - DEBUG - Command execution: stty -g 2>/dev/null
13:59:13 - DEBUG - Start interactor
[1] guard(main)> 

[thibaudgg]

Mmm that's weird,

• same issue when launching guard with bundle exec ? (or maybe you are using bin/stub)
• Have you a (~/).rspec file with some custom settings?

[jjb]

same issue when launching guard with bundle exec

same behavior. (but yes, i was using bin/stub)

Have you a (~/).rspec file with some custom settings?

➔ cat .rspec
--color
--format=documentation
➔ cat ~/.rspec
➔ 

removing .rspec does not change behavior

sorry this is taking so long... i hope it's not something stupid i'm overlooking...

[thibaudgg]

Ok I think, that I have found and fix this issue (it was coming from Guard notifier rewrite in 2.0). Please update guard-rspec (4.0.3) and it should be fine.

[jjb]

working now -- thank you!!!

[mufasa71]

@thibaudgg, @jjb Thanks guys, there was also bug with NotifySend after upgrading to 4.0.3, all fixed.

[thibaudgg]

Great, thanks for your feedback!