This comment was made on the wrong question. > On Aug 1, 2019, at 11:40 PM, Jack Royal-Gordon <jac...@pobox.com> wrote: > > Solved it. Do you know about hearing hoofbeats and thinking you’re hearing > zebras instead of horses? I was looking for a problem with the configuration > or upgraded versions or something arcane when in reality it was because I > made a code change that caused all the tests to fail (redirecting requests > that were made to a bare domain (no “www.”) to the canonical (www.) domain. > Ugh! > > Thanks for your help. > >> On Aug 1, 2019, at 5:08 PM, Jack Royal-Gordon <jac...@pobox.com >> <mailto:jac...@pobox.com>> wrote: >> >> Hi Jon, >> >> I tried Guard but ended up in dependency hell — kept loading things that >> said they needed Ruby 2.2 or later. After the fourth or fifth one, I gave >> up. For now, I’m concentrating on just RSpec and not worrying about autotest >> (I’ll keep trying both autotest and Guard as I migrate up to the more recent >> versions of Ruby/Rails). >> >> Thanks for your help on this. >> >> Jack >> >>> On Aug 1, 2019, at 12:24 AM, Jon Rowe <m...@jonrowe.co.uk >>> <mailto:m...@jonrowe.co.uk>> wrote: >>> >>> Hi Jack >>> >>> I’m suggesting you focus on getting a minimal auto test configuration >>> working before adding bits like growl etc :) Your errors now look like it’s >>> getting confused with minutest. I would seriously recommend trying guard >>> instead if you want to just run tour tests when files change! >>> >>> Autotest is not really a CI tool, it’s just a way of running your tests >>> when files change, so its completely different to a “commercial CI >>> solution”, you don’t need a CI solution if its just you working on your >>> project in my opinion. >>> >>> Cheers >>> Jon Rowe >>> --------------------------- >>> m...@jonrowe.co.uk <mailto:m...@jonrowe.co.uk> >>> jonrowe.co.uk <http://jonrowe.co.uk/> >>> >>> On 30 July 2019 at 01:15, Jack R-G wrote: >>>> Easier said than done, I think. Are you suggesting that I focus on >>>> minimizing my existing project, or are you suggesting that I focus on >>>> trying to get autotest working with a new, dummy project with minimal >>>> code? >>>> >>>> Also, do you have a solution that you like for CI on a personal >>>> development system - autotest was so simple to use (when I started using >>>> it), and I can't imagine doing the work to setup up one of the bigger >>>> commercial CI solutions like Jenkins or Travis. >>>> >>>> I got further (maybe) by removing some of the gem references from my >>>> Gemfile (autoest-fsevent, autotest-growl) and replacing them with just >>>> "autotest". I then did "bundle install". When I now run autotest, I get >>>> the following: >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/bin/ruby -I.:lib:test >>>> <i.:lib:test> -e "gem 'minitest'; %w[minitest/autorun >>>> test/performance/browsing_test.rb test/test_helper.rb >>>> test/unit/test_webhooks.rb].each { |f| require f }" -- --server 70284 >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/mocha-0.10.5/lib/mocha/integration/mini_test.rb:22:in >>>> `remove_method': method `run' not defined in Minitest::Unit::TestCase >>>> (NameError) >>>> >>>> from >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/mocha-0.10.5/lib/mocha/integration/mini_test.rb:22:in >>>> `<class:TestCase>' >>>> >>>> from >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/mocha-0.10.5/lib/mocha/integration/mini_test.rb:17:in >>>> `<class:Unit>' >>>> >>>> from >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/mocha-0.10.5/lib/mocha/integration/mini_test.rb:16:in >>>> `<module:MiniTest>' >>>> >>>> and >>>> Unhandled exception: undefined method `results' for >>>> #<Autotest:0x007f9b4b06fa20> >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/autotest-growl-0.2.16/lib/autotest/result.rb:7:in >>>> `initialize' >>>> >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/autotest-growl-0.2.16/lib/autotest/growl.rb:138:in >>>> `new' >>>> >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/autotest-growl-0.2.16/lib/autotest/growl.rb:138:in >>>> `block in <module:Growl>' >>>> >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:725:in >>>> `[]' >>>> >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:725:in >>>> `block in hook' >>>> >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:725:in >>>> `each' >>>> >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:725:in >>>> `any?' >>>> >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:725:in >>>> `hook' >>>> >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:314:in >>>> `run_tests' >>>> >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:292:in >>>> `get_to_green' >>>> >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:263:in >>>> `block in run' >>>> >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:261:in >>>> `loop' >>>> >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:261:in >>>> `run' >>>> >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/lib/autotest.rb:152:in >>>> `run' >>>> >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/lib/ruby/gems/2.0.0/gems/minitest-autotest-1.1.1/bin/autotest:5:in >>>> `<top (required)>' >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/bin/autotest:25:in `load' >>>> >>>> /Users/jackrg/.rbenv/versions/2.0.0-p576/bin/autotest:25:in `<main>' >>>> >>>> >>>> Any thoughts about these errors? >>>> >>>> On Monday, July 29, 2019 at 8:02:10 AM UTC-7, Jon Rowe wrote: >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "rspec" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to rspec+unsubscr...@googlegroups.com >>> <mailto:rspec+unsubscr...@googlegroups.com>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/rspec/dejalu-217-d111c00f-7926-4d6c-8ab2-aa8a0518aacd%40jonrowe.co.uk >>> >>> <https://groups.google.com/d/msgid/rspec/dejalu-217-d111c00f-7926-4d6c-8ab2-aa8a0518aacd%40jonrowe.co.uk?utm_medium=email&utm_source=footer>. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "rspec" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to rspec+unsubscr...@googlegroups.com >> <mailto:rspec+unsubscr...@googlegroups.com>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/rspec/B012E180-4EEE-40D9-B2A7-B3968BF6345E%40pobox.com >> >> <https://groups.google.com/d/msgid/rspec/B012E180-4EEE-40D9-B2A7-B3968BF6345E%40pobox.com?utm_medium=email&utm_source=footer>. > > > -- > You received this message because you are subscribed to the Google Groups > "rspec" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to rspec+unsubscr...@googlegroups.com > <mailto:rspec+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/rspec/97473C4B-88CF-4BBF-A1CE-0AAA0F5B045C%40pobox.com > > <https://groups.google.com/d/msgid/rspec/97473C4B-88CF-4BBF-A1CE-0AAA0F5B045C%40pobox.com?utm_medium=email&utm_source=footer>.
-- You received this message because you are subscribed to the Google Groups "rspec" group. To unsubscribe from this group and stop receiving emails from it, send an email to rspec+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rspec/3129B7D7-FC0C-4D05-9673-71A2D7D6B08C%40pobox.com.
