Hi,
I''ve been using the rspec and rspec_on_rails plugins quite happily on
my Rails project for a while now. Today I noticed the autotest
support in RSpec-1.0.3 and decided to give that a spin.
Oh tragedy!
$ autotest
loading autotest/rails_rspec
./vendor/plugins/rspec_on_rails/lib/autotest/rails_rspec.rb:33:in
`initialize'': undefined method `singularize'' for
"organizations":String (NoMethodError)
from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/
autotest.rb:395:in `call''
from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/
autotest.rb:395:in `tests_for_file''
from ./vendor/plugins/rspec/lib/autotest/rspec.rb:19:in
`tests_for_file''
from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/
autotest.rb:319:in `find_files_to_test''
from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/
autotest.rb:318:in `each''
from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/
autotest.rb:318:in `find_files_to_test''
from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/
autotest.rb:373:in `reset''
from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/
autotest.rb:164:in `run''
from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/
autotest.rb:123:in `run''
from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/bin/
autotest:48
from /usr/local/bin/autotest:18:in `load''
from /usr/local/bin/autotest:18
Hey, that''s not good.
RSpec is totally happy when I run it by itself, and RSpec + autotest
is totally happy when I run it in a fresh Rails project (as per the
1.0.3 announcement). It''s just freaking out on my current project and
I can''t get it to un-freak out no matter how many files I knock out.
Maybe this is a ZenTest problem instead. Maybe I''ve just done
something incredibly stupid in my Rails project to break everything
(but everything else works fine!). I don''t know. I''m
desperate. I
really, really want autotest to work. Can anyone help?
Cheers,
-Tom
On 5/30/07, Tom Stuart <tom at experthuman.com> wrote:> Hi, > > I''ve been using the rspec and rspec_on_rails plugins quite happily on > my Rails project for a while now. Today I noticed the autotest > support in RSpec-1.0.3 and decided to give that a spin. > > Oh tragedy! > > $ autotest > loading autotest/rails_rspec > ./vendor/plugins/rspec_on_rails/lib/autotest/rails_rspec.rb:33:in > `initialize'': undefined method `singularize'' for > "organizations":String (NoMethodError) > from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/ > autotest.rb:395:in `call'' > from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/ > autotest.rb:395:in `tests_for_file'' > from ./vendor/plugins/rspec/lib/autotest/rspec.rb:19:in > `tests_for_file'' > from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/ > autotest.rb:319:in `find_files_to_test'' > from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/ > autotest.rb:318:in `each'' > from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/ > autotest.rb:318:in `find_files_to_test'' > from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/ > autotest.rb:373:in `reset'' > from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/ > autotest.rb:164:in `run'' > from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/lib/ > autotest.rb:123:in `run'' > from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.6.0/bin/ > autotest:48 > from /usr/local/bin/autotest:18:in `load'' > from /usr/local/bin/autotest:18 > > Hey, that''s not good. > > RSpec is totally happy when I run it by itself, and RSpec + autotest > is totally happy when I run it in a fresh Rails project (as per the > 1.0.3 announcement). It''s just freaking out on my current project and > I can''t get it to un-freak out no matter how many files I knock out. > > Maybe this is a ZenTest problem instead. Maybe I''ve just done > something incredibly stupid in my Rails project to break everything > (but everything else works fine!). I don''t know. I''m desperate. I > really, really want autotest to work. Can anyone help?Check out this bug report: http://rubyforge.org/tracker/?func=detail&atid=3151&aid=11221&group_id=797 A change is in the works. Cheers, David> > Cheers, > -Tom > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
On 30 May 2007, at 21:52, David Chelimsky wrote:> Check out this bug report: > http://rubyforge.org/tracker/? > func=detail&atid=3151&aid=11221&group_id=797 > A change is in the works.Oh, that''s awesome. Easily fixed. Thank you so much. Cheers, -Tom
On 5/30/07, Tom Stuart <tom at experthuman.com> wrote:> On 30 May 2007, at 21:52, David Chelimsky wrote: > > Check out this bug report: > > http://rubyforge.org/tracker/? > > func=detail&atid=3151&aid=11221&group_id=797 > > A change is in the works. > > Oh, that''s awesome. Easily fixed. Thank you so much.So did you apply Josh''s 2nd patch and watch the problem disappear?> > Cheers, > -Tom > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
On 30 May 2007, at 22:13, David Chelimsky wrote:>> Easily fixed. > So did you apply Josh''s 2nd patch and watch the problem disappear?Yep! Everything''s happy again now, especially me.
On 5/30/07, Tom Stuart <tom at experthuman.com> wrote:> On 30 May 2007, at 22:13, David Chelimsky wrote: > >> Easily fixed. > > So did you apply Josh''s 2nd patch and watch the problem disappear? > > Yep! Everything''s happy again now, especially me.:) Thanks.> _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
On 5/30/07, Tom Stuart <tom at experthuman.com> wrote:> > > Yep! Everything''s happy again now, especially me.Good to hear. Sorry I broke it the first time! Josh -- Josh Knowles joshknowles at gmail.com http://joshknowles.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20070530/7c9d426e/attachment.html
On 5/30/07, Josh Knowles <joshknowles at gmail.com> wrote:> > > On 5/30/07, Tom Stuart <tom at experthuman.com> wrote: > > > > Yep! Everything''s happy again now, especially me. > > > Good to hear. Sorry I broke it the first time!Thanks for fixing it so fast. David> > Josh > > > > > -- > Josh Knowles > joshknowles at gmail.com > http://joshknowles.com > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
On 30 May 2007, at 22:17, Tom Stuart wrote:> Everything''s happy again now, especially me.I''ve stopped being happy again, although this time for a different reason! I''ve got (let''s say) one spec, with (let''s say) 10 examples in it. autotest + rspec work like a charm as long all the examples pass, but if I change my code so that (let''s say) 4 of the examples fail, things start to get out of control. autotest runs automatically after I make the broken change, which is fine:> script/spec -O spec/spec.opts spec/models/matcher_spec.rb > FFFF......But then if I just touch a file so that it runs again, it does this:> script/spec -O spec/spec.opts spec/models/matcher_spec.rb; script/ > spec -O spec/spec.opts spec/models/matcher_spec.rb; script/spec -O > spec/spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > spec.opts spec/models/matcher_spec.rb > FFFF...... > FFFF...... > FFFF...... > FFFF......And if I touch again, I get:> script/spec -O spec/spec.opts spec/models/matcher_spec.rb; script/ > spec -O spec/spec.opts spec/models/matcher_spec.rb; script/spec -O > spec/spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > spec.opts spec/models/matcher_spec.rb; [...16 times...] > FFFF...... > FFFF...... > FFFF...... > FFFF...... > FFFF...... > FFFF...... > [...16 times...]As you can imagine, as time goes by, this isn''t doing much for my productivity. If I actually fix the breakage so that all the examples pass again, and wait for the 4^n invocations of script/spec to finish, I''m back in a healthy sitaution again, but once more examples start failing it starts spiraling off again... This is all a great incentive to never break my code but I need something a little gentler for now. Before I spend too much time investigating it, does anyone have any intuition about whether this is a zentest or an rspec_on_rails issue? Cheers, -Tom
On 5/31/07, Tom Stuart <tom at experthuman.com> wrote:> On 30 May 2007, at 22:17, Tom Stuart wrote: > > Everything''s happy again now, especially me. > > I''ve stopped being happy again, although this time for a different > reason! > > I''ve got (let''s say) one spec, with (let''s say) 10 examples in it. > autotest + rspec work like a charm as long all the examples pass, but > if I change my code so that (let''s say) 4 of the examples fail, > things start to get out of control. > > autotest runs automatically after I make the broken change, which is > fine: > > > script/spec -O spec/spec.opts spec/models/matcher_spec.rb > > FFFF...... > > But then if I just touch a file so that it runs again, it does this: > > > script/spec -O spec/spec.opts spec/models/matcher_spec.rb; script/ > > spec -O spec/spec.opts spec/models/matcher_spec.rb; script/spec -O > > spec/spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > > spec.opts spec/models/matcher_spec.rb > > FFFF...... > > FFFF...... > > FFFF...... > > FFFF...... > > And if I touch again, I get: > > > script/spec -O spec/spec.opts spec/models/matcher_spec.rb; script/ > > spec -O spec/spec.opts spec/models/matcher_spec.rb; script/spec -O > > spec/spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > > spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > > spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > > spec.opts spec/models/matcher_spec.rb; [...16 times...] > > FFFF...... > > FFFF...... > > FFFF...... > > FFFF...... > > FFFF...... > > FFFF...... > > [...16 times...] > > As you can imagine, as time goes by, this isn''t doing much for my > productivity. If I actually fix the breakage so that all the examples > pass again, and wait for the 4^n invocations of script/spec to > finish, I''m back in a healthy sitaution again, but once more examples > start failing it starts spiraling off again... > > This is all a great incentive to never break my code but I need > something a little gentler for now. Before I spend too much time > investigating it, does anyone have any intuition about whether this > is a zentest or an rspec_on_rails issue?I''ve not heard of this before and can''t reproduce it. Which file are you touching to get this to happen?> > Cheers, > -Tom > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
On 5/31/07, David Chelimsky <dchelimsky at gmail.com> wrote:> On 5/31/07, Tom Stuart <tom at experthuman.com> wrote: > > I''ve stopped being happy again, although this time for a different > > reason! > > > > I''ve got (let''s say) one spec, with (let''s say) 10 examples in it. > > autotest + rspec work like a charm as long all the examples pass, but > > if I change my code so that (let''s say) 4 of the examples fail, > > things start to get out of control. > > > > autotest runs automatically after I make the broken change, which is > > fine: > > > > > script/spec -O spec/spec.opts spec/models/matcher_spec.rb > > > FFFF...... > > > > But then if I just touch a file so that it runs again, it does this: > > > > > script/spec -O spec/spec.opts spec/models/matcher_spec.rb; script/ > > > spec -O spec/spec.opts spec/models/matcher_spec.rb; script/spec -O > > > spec/spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > > > spec.opts spec/models/matcher_spec.rb > > > FFFF...... > > > FFFF...... > > > FFFF...... > > > FFFF...... > > > > And if I touch again, I get: > > > > > script/spec -O spec/spec.opts spec/models/matcher_spec.rb; script/ > > > spec -O spec/spec.opts spec/models/matcher_spec.rb; script/spec -O > > > spec/spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > > > spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > > > spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > > > spec.opts spec/models/matcher_spec.rb; [...16 times...] > > > FFFF...... > > > FFFF...... > > > FFFF...... > > > FFFF...... > > > FFFF...... > > > FFFF...... > > > [...16 times...] > > > > As you can imagine, as time goes by, this isn''t doing much for my > > productivity. If I actually fix the breakage so that all the examples > > pass again, and wait for the 4^n invocations of script/spec to > > finish, I''m back in a healthy sitaution again, but once more examples > > start failing it starts spiraling off again... > > > > This is all a great incentive to never break my code but I need > > something a little gentler for now. Before I spend too much time > > investigating it, does anyone have any intuition about whether this > > is a zentest or an rspec_on_rails issue? > > I''ve not heard of this before and can''t reproduce it. Which file are > you touching to get this to happen?I have the same issue. I typically only notice when working on a controller, since my controller specs are often larger than my model or view specs, so 16+ runs can take quite a while, but it happens with everything AFAICT. As an example to recap: Turn on autotest, get my green. Comment out the Model.find(:all) from my index action, save, and get 2 failures. Save again without changing anything, get the same 2 failures, but autotest runs a second time. Save once more, autotest runs four times. Again, 8. And so on. I''m currently running Rails r6868, rspec+rspec_on_rails r2049, and ZenTest 3.6.0 on OS X 10.4.9. Also using growlnotify with a .autotest I found at http://blog.internautdesign.com/2006/11/12/autotest-growl-goodness. Any other information that could help? Kyle
On 31 May 2007, at 12:41, David Chelimsky wrote:> I''ve not heard of this before and can''t reproduce it.Below is how I can reproduce on a fresh Rails project. Does this work for you too, or is it something weird about my environment? (Note that, once autotest is running, I''ve simply inserted its subsequent output below each command that prompted it, for lack of any better way of showing the activity in two concurrent windows.) Cheers, -Tom -- ~$ uname -a Linux 2.6.20-16-server #2 SMP Wed May 23 01:53:06 UTC 2007 i686 GNU/ Linux ~$ ruby -v ruby 1.8.5 (2006-08-25) [i486-linux] ~$ rails -v Rails 1.2.3 ~$ zentest -v zentest v3.6.0 ~$ rails myproject ~$ mysqladmin -u root create myproject_development ~$ cd myproject/ ~/myproject$ ./script/plugin install svn://rubyforge.org/var/svn/ rspec/trunk/rspec ~/myproject$ ./script/plugin install svn://rubyforge.org/var/svn/ rspec/trunk/rspec_on_rails ~/myproject$ ./script/generate rspec ~/myproject$ ./script/generate rspec_scaffold Post title:string body:text ~/myproject$ rake db:migrate ~/myproject$ autotest script/spec -O spec/spec.opts spec/views/posts/new.rhtml_spec.rb spec/ views/posts/index.rhtml_spec.rb spec/views/posts/show.rhtml_spec.rb spec/controllers/posts_controller_spec.rb spec/views/posts/ edit.rhtml_spec.rb spec/helpers/posts_helper_spec.rb spec/models/ post_spec.rb ........................................... 43 examples, 0 failures ~/myproject$ sed -ie ''5,10s/^/#/'' app/controllers/posts_controller.rb script/spec -O spec/spec.opts spec/controllers/posts_controller_spec.rb .........................FF.FF........ 38 examples, 4 failures ~/myproject$ touch app/controllers/posts_controller.rb script/spec -O spec/spec.opts spec/controllers/ posts_controller_spec.rb; script/spec -O spec/spec.opts spec/ controllers/posts_controller_spec.rb .........................FF.FF........ 38 examples, 4 failures .........................FF.FF........ 38 examples, 4 failures ~/myproject$ touch app/controllers/posts_controller.rb script/spec -O spec/spec.opts spec/controllers/ posts_controller_spec.rb; script/spec -O spec/spec.opts spec/ controllers/posts_controller_spec.rb; script/spec -O spec/spec.opts spec/controllers/posts_controller_spec.rb; script/spec -O spec/ spec.opts spec/controllers/posts_controller_spec.rb .........................FF.FF........ 38 examples, 4 failures .........................FF.FF........ 38 examples, 4 failures .........................FF.FF........ 38 examples, 4 failures .........................FF.FF........ 38 examples, 4 failures ~/myproject$ sed -ie ''5,10s/^#//'' app/controllers/posts_controller.rb script/spec -O spec/spec.opts spec/controllers/ posts_controller_spec.rb; script/spec -O spec/spec.opts spec/ controllers/posts_controller_spec.rb; script/spec -O spec/spec.opts spec/controllers/posts_controller_spec.rb; script/spec -O spec/ spec.opts spec/controllers/posts_controller_spec.rb; script/spec -O spec/spec.opts spec/controllers/posts_controller_spec.rb; script/ spec -O spec/spec.opts spec/controllers/posts_controller_spec.rb; script/spec -O spec/spec.opts spec/controllers/ posts_controller_spec.rb; script/spec -O spec/spec.opts spec/ controllers/posts_controller_spec.rb ...................................... 38 examples, 0 failures ...................................... 38 examples, 0 failures ...................................... 38 examples, 0 failures ...................................... 38 examples, 0 failures ...................................... 38 examples, 0 failures ...................................... 38 examples, 0 failures ...................................... 38 examples, 0 failures ...................................... 38 examples, 0 failures script/spec -O spec/spec.opts spec/views/posts/new.rhtml_spec.rb spec/ views/posts/index.rhtml_spec.rb spec/views/posts/show.rhtml_spec.rb spec/controllers/posts_controller_spec.rb spec/views/posts/ edit.rhtml_spec.rb spec/helpers/posts_helper_spec.rb spec/models/ post_spec.rb ........................................... 43 examples, 0 failures ~/myproject$ touch app/controllers/posts_controller.rb script/spec -O spec/spec.opts spec/controllers/posts_controller_spec.rb ...................................... 38 examples, 0 failures
On 5/31/07, Kyle Hargraves <philodespotos at gmail.com> wrote:> On 5/31/07, David Chelimsky <dchelimsky at gmail.com> wrote: > > On 5/31/07, Tom Stuart <tom at experthuman.com> wrote: > > > I''ve stopped being happy again, although this time for a different > > > reason! > > > > > > I''ve got (let''s say) one spec, with (let''s say) 10 examples in it. > > > autotest + rspec work like a charm as long all the examples pass, but > > > if I change my code so that (let''s say) 4 of the examples fail, > > > things start to get out of control. > > > > > > autotest runs automatically after I make the broken change, which is > > > fine: > > > > > > > script/spec -O spec/spec.opts spec/models/matcher_spec.rb > > > > FFFF...... > > > > > > But then if I just touch a file so that it runs again, it does this: > > > > > > > script/spec -O spec/spec.opts spec/models/matcher_spec.rb; script/ > > > > spec -O spec/spec.opts spec/models/matcher_spec.rb; script/spec -O > > > > spec/spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > > > > spec.opts spec/models/matcher_spec.rb > > > > FFFF...... > > > > FFFF...... > > > > FFFF...... > > > > FFFF...... > > > > > > And if I touch again, I get: > > > > > > > script/spec -O spec/spec.opts spec/models/matcher_spec.rb; script/ > > > > spec -O spec/spec.opts spec/models/matcher_spec.rb; script/spec -O > > > > spec/spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > > > > spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > > > > spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ > > > > spec.opts spec/models/matcher_spec.rb; [...16 times...] > > > > FFFF...... > > > > FFFF...... > > > > FFFF...... > > > > FFFF...... > > > > FFFF...... > > > > FFFF...... > > > > [...16 times...] > > > > > > As you can imagine, as time goes by, this isn''t doing much for my > > > productivity. If I actually fix the breakage so that all the examples > > > pass again, and wait for the 4^n invocations of script/spec to > > > finish, I''m back in a healthy sitaution again, but once more examples > > > start failing it starts spiraling off again... > > > > > > This is all a great incentive to never break my code but I need > > > something a little gentler for now. Before I spend too much time > > > investigating it, does anyone have any intuition about whether this > > > is a zentest or an rspec_on_rails issue? > > > > I''ve not heard of this before and can''t reproduce it. Which file are > > you touching to get this to happen? > > I have the same issue. I typically only notice when working on a > controller, since my controller specs are often larger than my model > or view specs, so 16+ runs can take quite a while, but it happens with > everything AFAICT. > > As an example to recap: Turn on autotest, get my green. Comment out > the Model.find(:all) from my index action, save, and get 2 failures. > Save again without changing anything, get the same 2 failures, but > autotest runs a second time. Save once more, autotest runs four times. > Again, 8. And so on. > > I''m currently running Rails r6868, rspec+rspec_on_rails r2049, and > ZenTest 3.6.0 on OS X 10.4.9. > Also using growlnotify with a .autotest I found at > http://blog.internautdesign.com/2006/11/12/autotest-growl-goodness.I added the growl file described and get the following error: ./.autotest:7:in `slice'': can''t convert Regexp into Integer (TypeError) Did you run into this problem?> > Any other information that could help? > > Kyle > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
Jonathan Linowes
2007-May-31 16:33 UTC
[rspec-users] autotest and rspec_on_rails not happy
This is exactly what happens to me too On May 31, 2007, at 7:41 AM, David Chelimsky wrote:> On 5/31/07, Tom Stuart <tom at experthuman.com> wrote: >> On 30 May 2007, at 22:17, Tom Stuart wrote: >>> Everything''s happy again now, especially me. >> >> I''ve stopped being happy again, although this time for a different >> reason! >> >> I''ve got (let''s say) one spec, with (let''s say) 10 examples in it. >> autotest + rspec work like a charm as long all the examples pass, but >> if I change my code so that (let''s say) 4 of the examples fail, >> things start to get out of control. >> >> autotest runs automatically after I make the broken change, which is >> fine: >> >>> script/spec -O spec/spec.opts spec/models/matcher_spec.rb >>> FFFF...... >> >> But then if I just touch a file so that it runs again, it does this: >> >>> script/spec -O spec/spec.opts spec/models/matcher_spec.rb; script/ >>> spec -O spec/spec.opts spec/models/matcher_spec.rb; script/spec -O >>> spec/spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ >>> spec.opts spec/models/matcher_spec.rb >>> FFFF...... >>> FFFF...... >>> FFFF...... >>> FFFF...... >> >> And if I touch again, I get: >> >>> script/spec -O spec/spec.opts spec/models/matcher_spec.rb; script/ >>> spec -O spec/spec.opts spec/models/matcher_spec.rb; script/spec -O >>> spec/spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ >>> spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ >>> spec.opts spec/models/matcher_spec.rb; script/spec -O spec/ >>> spec.opts spec/models/matcher_spec.rb; [...16 times...] >>> FFFF...... >>> FFFF...... >>> FFFF...... >>> FFFF...... >>> FFFF...... >>> FFFF...... >>> [...16 times...] >> >> As you can imagine, as time goes by, this isn''t doing much for my >> productivity. If I actually fix the breakage so that all the examples >> pass again, and wait for the 4^n invocations of script/spec to >> finish, I''m back in a healthy sitaution again, but once more examples >> start failing it starts spiraling off again... >> >> This is all a great incentive to never break my code but I need >> something a little gentler for now. Before I spend too much time >> investigating it, does anyone have any intuition about whether this >> is a zentest or an rspec_on_rails issue? > > I''ve not heard of this before and can''t reproduce it. Which file are > you touching to get this to happen? > >> >> Cheers, >> -Tom >> _______________________________________________ >> rspec-users mailing list >> rspec-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/rspec-users >> > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users
On 5/31/07, David Chelimsky <dchelimsky at gmail.com> wrote:> I added the growl file described and get the following error: > > ./.autotest:7:in `slice'': can''t convert Regexp into Integer (TypeError) > > Did you run into this problem?My mistake, I just provided the first link that looked similar on Google. That one''s for an older version of ZenTest that provided the results differently. The actual one I''m using is slightly different and I can''t find the blog I got it from, but this is my actual file: http://pastie.caboo.se/66587. Either way it looks to be irrelevant, as if I move the file out of the way and try it, the error still occurs. Kyle
On 31 May 2007, at 15:11, Tom Stuart wrote:> On 31 May 2007, at 12:41, David Chelimsky wrote: >> I''ve not heard of this before and can''t reproduce it. > Below is how I can reproduce on a fresh Rails project.Was anyone (e.g. David) able to reproduce this, let alone fix it? autotest is integral to my workflow so this bug (if that''s what it is) is essentially preventing me from using RSpec. If anybody has any vague ideas or suggestions about where to start investigating then I''ll do so, but I don''t know anything about RSpec/ZenTest internals so I don''t want to go in completely blind. Cheers, -Tom
On 6/5/07, Tom Stuart <tom at experthuman.com> wrote:> On 31 May 2007, at 15:11, Tom Stuart wrote: > > On 31 May 2007, at 12:41, David Chelimsky wrote: > >> I''ve not heard of this before and can''t reproduce it. > > Below is how I can reproduce on a fresh Rails project. > > Was anyone (e.g. David) able to reproduce this, let alone fix it?If I understand the problem correctly, this is fixed in trunk: http://rubyforge.org/tracker/index.php?func=detail&aid=11337&group_id=797&atid=3149> > autotest is integral to my workflow so this bug (if that''s what it > is) is essentially preventing me from using RSpec. If anybody has any > vague ideas or suggestions about where to start investigating then > I''ll do so, but I don''t know anything about RSpec/ZenTest internals > so I don''t want to go in completely blind. > > Cheers, > -Tom > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
On 5 Jun 2007, at 12:33, David Chelimsky wrote:>> Was anyone (e.g. David) able to reproduce this, let alone fix it? > If I understand the problem correctly, this is fixed in trunk:Magical. This is indeed fixed since r2076. Thank you!
Wincent Colaiuta
2007-Jun-05 11:50 UTC
[rspec-users] autotest and rspec_on_rails not happy
El 5/6/2007, a las 12:59, Tom Stuart escribi?:> On 31 May 2007, at 15:11, Tom Stuart wrote: >> On 31 May 2007, at 12:41, David Chelimsky wrote: >>> I''ve not heard of this before and can''t reproduce it. >> Below is how I can reproduce on a fresh Rails project. > > Was anyone (e.g. David) able to reproduce this, let alone fix it? > > autotest is integral to my workflow so this bug (if that''s what it > is) is essentially preventing me from using RSpec. If anybody has any > vague ideas or suggestions about where to start investigating then > I''ll do so, but I don''t know anything about RSpec/ZenTest internals > so I don''t want to go in completely blind.I''ve seen this as well, although not lately. If I see it again I''ll try to distill it down to a reproducible case. Cheers, Wincent