> Yes - I sometimes get the spec_server timeout as well - but I usually don't. > > Try running just against just one environment: > > rake rspec:pre_commit > > without the -f option.
tried that (it runs against edge) and it still won't wor. I'm still getting the timeouts: Pending: should have_tag should report the correct line number for a nested failed test/unit assertion (Doesn't work at the moment. Do we want to support this?) A controller spec a spec in a context without controller_name set should fail with a useful warning (need a new way to deal with examples that should_raise) A controller spec a spec in a context without controller_name set should fail with a useful warning (need a new way to deal with examples that should_raise) 1) Timeout::Error in 'script/spec_server file with TextMate bundle runs a spec' execution expired 2) Timeout::Error in 'script/spec_server file without TextMate bundle runs a spec' execution expired Finished in 24.298229 seconds 332 examples, 2 failures, 3 pending rake aborted! ERROR while running rake: rake spec:plugins:rspec_on_rails --trace /Users/rupert/stuff/downloads/rspec/rspec/pre_commit/lib/pre_commit/pre_commit.rb:19:in `rake_sh' /Users/rupert/stuff/downloads/rspec/rspec/pre_commit/lib/pre_commit/rspec_on_rails.rb:44:in `rspec_pre_commit' /Users/rupert/stuff/downloads/rspec/example_rails_app/lib/tasks/bootstrap_rspec.rake:11 /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:546:in `call' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:546:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:541:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:541:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:508:in `invoke_with_call_chain' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in `synchronize' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in `invoke_with_call_chain' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:494:in `invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1931:in `invoke_task' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1909:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1909:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1909:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1948:in `standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1903:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1881:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1948:in `standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake.rb:1878:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.1/bin/rake:31 /usr/local/bin/rake:19:in `load' /usr/local/bin/rake:19 Is there something I can comment out to remove the offending bits from the run? Cheers Rupert _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
