using format (-f) option creates duplicate output

[goosetav]

trafficstars

happens with both spring rspec and ./bin/rspec

happens with both released gem and current master branch aebd5d87c07a4f0f0d025aa25129cc3cb6d54c71

# spring rspec spec/models/app_spec.rb

Run options:
  include {:focus=>true}
  exclude {:broken=>true}

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

Finished in 0.14627 seconds (files took 0.23199 seconds to load)
4 examples, 0 failures

Randomized with seed 64426

# spring rspec -f progress spec/models/app_spec.rb
Run options:
  include {:focus=>true}
  exclude {:broken=>true}
Run options:
  include {:focus=>true}
  exclude {:broken=>true}

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

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


Finished in 0.15579 seconds (files took 0.27696 seconds to load)
4 examples, 0 failures

Finished in 0.15579 seconds (files took 0.27696 seconds to load)
4 examples, 0 failures

Randomized with seed 64426


Randomized with seed 64426

without spring:

# bundle exec rspec -f progress spec/models/app_spec.rb 
Run options:
  include {:focus=>true}
  exclude {:broken=>true}

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

Finished in 0.11127 seconds (files took 10.19 seconds to load)
4 examples, 0 failures

Randomized with seed 54966

[mkcode]

+1. This happens to me as well. Only upon upgrading from rspec 2 to 3 did it start.

[mkcode]

@goosetav - I was able to fix this by adding 'require: false' to the 'guard-rspec' gem in Gemfile as it is described in the guard-rspec readme.

This issue is raised on the wrong project and is a RTFM for guard-rspec.