I seem to remember when I was running a previous version of rspec and autotest that when a set of specs passed for some changed files, that all of the specs would then be run automatically. Particularly when tests had previously failed. It''s not doing it now on trunk. Was I imagining this, or is something wrong? Thanks, Steve
On Feb 15, 2008 6:06 PM, Steve <vertebrate at gmail.com> wrote:> I seem to remember when I was running a previous version of rspec and > autotest that when a set of specs passed for some changed files, that all > of the specs would then be run automatically. Particularly when tests had > previously failed. It''s not doing it now on trunk. Was I imagining this, > or is something wrong?Something was wrong, but it''s fixed now in trunk.> > Thanks, > Steve > > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
On Sat, 16 Feb 2008 10:23:53 -0500, David Chelimsky wrote:> On Feb 15, 2008 6:06 PM, Steve > <vertebrate at gmail.com> wrote: >> I seem to remember when I was running a previous version of rspec and >> autotest that when a set of specs passed for some changed files, that >> all of the specs would then be run automatically. Particularly when >> tests had previously failed. It''s not doing it now on trunk. Was I >> imagining this, or is something wrong? > > Something was wrong, but it''s fixed now in trunk. >What was the nature of the changes. I just updated to r3312, and when I run autotest I get: loading autotest/rails_rspec /usr/bin/ruby1.8 -S script/spec -O spec/spec.opts <all the specs> No server is running I''ve never seen the "No server is running" message before. Steve
On Sat, 16 Feb 2008 18:13:51 +0000, Steve wrote:> What was the nature of the changes. I just updated to r3312, and when I > run autotest I get: > > loading autotest/rails_rspec > /usr/bin/ruby1.8 -S script/spec -O spec/spec.opts <all the specs> No > server is running > > I''ve never seen the "No server is running" message before.Cancel that. I had --drb in spec.opts, and it looks like there was a commit to make that work. Funny I never noticed that before.
On Feb 16, 2008 1:21 PM, Steve <vertebrate at gmail.com> wrote:> On Sat, 16 Feb 2008 18:13:51 +0000, Steve wrote: > > What was the nature of the changes. I just updated to r3312, and when I > > run autotest I get: > > > > loading autotest/rails_rspec > > /usr/bin/ruby1.8 -S script/spec -O spec/spec.opts <all the specs> No > > server is running > > > > I''ve never seen the "No server is running" message before. > > Cancel that. I had --drb in spec.opts, and it looks like there was a > commit to make that work. Funny I never noticed that before.It was broken until a recent changeset :)> > > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
On Sat, Feb 16, 2008 at 10:39 AM, David Chelimsky <dchelimsky at gmail.com> wrote:> On Feb 16, 2008 1:21 PM, Steve <vertebrate at gmail.com> wrote: > > On Sat, 16 Feb 2008 18:13:51 +0000, Steve wrote: > > > What was the nature of the changes. I just updated to r3312, and when I > > > run autotest I get: > > > > > > loading autotest/rails_rspec > > > /usr/bin/ruby1.8 -S script/spec -O spec/spec.opts <all the specs> No > > > server is running > > > > > > I''ve never seen the "No server is running" message before. > > > > Cancel that. I had --drb in spec.opts, and it looks like there was a > > commit to make that work. Funny I never noticed that before. > > It was broken until a recent changeset :)I don''t think it''s working quite right. 1) ''A puzzle if rejected, when resaved, should be re-submitted'' FAILED expected rejected? to return true, got false /Users/joe/projects/tanga/vendor/plugins/rspec/lib/spec/expectations.rb:52:in `fail_with'' /Users/joe/projects/tanga/vendor/plugins/rspec/lib/spec/expectations/handler.rb:21:in `handle_matcher'' /Users/joe/projects/tanga/vendor/plugins/rspec/lib/spec/expectations/extensions/object.rb:34:in `should'' ./spec/models/puzzle_spec.rb:187: Then this is the next executation: ruby -S script/spec -O spec/spec.opts spec/models/puzzle_spec.rb /Users/joe/projects/tanga/vendor/plugins/rspec/lib/spec/expectations.rb So it thiks that some rspec file was the cause of the crash. If the exception was raised from inside the Rails framework, then it tries to re-run the Rails file, and that sometimes really messes things up. Joe
On Wed, Feb 20, 2008 at 10:41 PM, Joe Van Dyk <joe at pinkpucker.net> wrote:> On Sat, Feb 16, 2008 at 10:39 AM, David Chelimsky <dchelimsky at gmail.com> wrote: > > On Feb 16, 2008 1:21 PM, Steve <vertebrate at gmail.com> wrote: > > > On Sat, 16 Feb 2008 18:13:51 +0000, Steve wrote: > > > > What was the nature of the changes. I just updated to r3312, and when I > > > > run autotest I get: > > > > > > > > loading autotest/rails_rspec > > > > /usr/bin/ruby1.8 -S script/spec -O spec/spec.opts <all the specs> No > > > > server is running > > > > > > > > I''ve never seen the "No server is running" message before. > > > > > > Cancel that. I had --drb in spec.opts, and it looks like there was a > > > commit to make that work. Funny I never noticed that before. > > > > It was broken until a recent changeset :) > > I don''t think it''s working quite right. > > 1) > ''A puzzle if rejected, when resaved, should be re-submitted'' FAILED > expected rejected? to return true, got false > /Users/joe/projects/tanga/vendor/plugins/rspec/lib/spec/expectations.rb:52:in > `fail_with'' > /Users/joe/projects/tanga/vendor/plugins/rspec/lib/spec/expectations/handler.rb:21:in > `handle_matcher'' > /Users/joe/projects/tanga/vendor/plugins/rspec/lib/spec/expectations/extensions/object.rb:34:in > `should'' > ./spec/models/puzzle_spec.rb:187: > > Then this is the next executation: > ruby -S script/spec -O spec/spec.opts spec/models/puzzle_spec.rb > /Users/joe/projects/tanga/vendor/plugins/rspec/lib/spec/expectations.rb > > So it thiks that some rspec file was the cause of the crash. If the > exception was raised from inside the Rails framework, then it tries to > re-run the Rails file, and that sometimes really messes things up.What rspec revision?> > Joe > > > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
On Thu, Feb 21, 2008 at 5:21 AM, David Chelimsky <dchelimsky at gmail.com> wrote:> > On Wed, Feb 20, 2008 at 10:41 PM, Joe Van Dyk <joe at pinkpucker.net> wrote: > > On Sat, Feb 16, 2008 at 10:39 AM, David Chelimsky <dchelimsky at gmail.com> wrote: > > > On Feb 16, 2008 1:21 PM, Steve <vertebrate at gmail.com> wrote: > > > > On Sat, 16 Feb 2008 18:13:51 +0000, Steve wrote: > > > > > What was the nature of the changes. I just updated to r3312, and when I > > > > > run autotest I get: > > > > > > > > > > loading autotest/rails_rspec > > > > > /usr/bin/ruby1.8 -S script/spec -O spec/spec.opts <all the specs> No > > > > > server is running > > > > > > > > > > I''ve never seen the "No server is running" message before. > > > > > > > > Cancel that. I had --drb in spec.opts, and it looks like there was a > > > > commit to make that work. Funny I never noticed that before. > > > > > > It was broken until a recent changeset :) > > > > I don''t think it''s working quite right. > > > > 1) > > ''A puzzle if rejected, when resaved, should be re-submitted'' FAILED > > expected rejected? to return true, got false > > /Users/joe/projects/tanga/vendor/plugins/rspec/lib/spec/expectations.rb:52:in > > `fail_with'' > > /Users/joe/projects/tanga/vendor/plugins/rspec/lib/spec/expectations/handler.rb:21:in > > `handle_matcher'' > > /Users/joe/projects/tanga/vendor/plugins/rspec/lib/spec/expectations/extensions/object.rb:34:in > > `should'' > > ./spec/models/puzzle_spec.rb:187: > > > > Then this is the next executation: > > ruby -S script/spec -O spec/spec.opts spec/models/puzzle_spec.rb > > /Users/joe/projects/tanga/vendor/plugins/rspec/lib/spec/expectations.rb > > > > So it thiks that some rspec file was the cause of the crash. If the > > exception was raised from inside the Rails framework, then it tries to > > re-run the Rails file, and that sometimes really messes things up. > > What rspec revision?trunk as of yesterday.