jstorimer/spin — Issue #18: RSpec 
Author: ashmoran
Created: 2011-11-14 11:49:50+00:00
State: open

I'm trying Spin for the first time. Using RSpec, the run time report seems to be showing the elapsed time since the pre-forked Rails process was started.

Has anyone seen this? Is it a bug in Spin, in RSpec or could it be something in this Rails app? (I get the same result with `spin serve --rspec` as well as through Guard)

✗ guard
Guard::Spin Initialized
Guard is now watching at '/Users/ashleymoran/Documents/PatchSpace/Development/bc'
Bundle already up-to-date
Starting Spin
LiveReload 1.6 is waiting for a browser to connect.
Preloaded Rails env in 9.81913s...
Spinning up spec/models/note_spec.rb

Loading ["spec/models/note_spec.rb"]
No examples matched {:wip=>true}. Running all.
No examples found.
0 examples: 100% |==========================================| Time: 00:00:00

Finished in 14.07 seconds
0 examples, 0 failures
Spinning up spec/models/note_spec.rb

Loading ["spec/models/note_spec.rb"]
No examples matched {:wip=>true}. Running all.
No examples found.
0 examples: 100% |==========================================| Time: 00:00:00

Finished in 39.17 seconds
0 examples, 0 failures
Spinning up spec/models/note_spec.rb

Loading ["spec/models/note_spec.rb"]
No examples matched {:wip=>true}. Running all.
No examples found.
0 examples: 100% |==========================================| Time: 00:00:00

Finished in 196.8 seconds
0 examples, 0 failures