7315 1 true 2008-08-22T19:03:09+02:00 24 2009-01-11T00:00:00+01:00 21779 503 rspec-fails-to-finish-running-properly-depending-on-load-order 16 5645 resolved bug patch 2008-11-28T17:34:16+01:00 7315 David Chelimsky eventualbuddha David Chelimsky http://rspec.lighthouseapp.com/projects/5645/tickets/503 1.1.12 This is the error that occurs: /var/lib/gems/1.8/gems/rspec-1.1.4/lib/spec.rb:27:in `exit?': undefined method `run?' for Test::Unit:Module (NoMethodError) from /var/lib/gems/1.8/gems/rspec-1.1.4/lib/spec/runner.rb:193:in `register_at_exit_hook' from spec/dsl_spec.rb:3 This doesn't happen on every machine, but it happens every time on my Ubuntu Linux 64-bit continuous integration machine when the following are true: 1) RSpec is loaded while Object.const_defined?(:Test) is false 2) Spec.exit? is called while Object.const_defined?(:Test) is true 3) test/unit has not been loaded My particular way to cause this was to have a spec_helper.rb file that looked like this: require 'rubygems' require 'spec' require File.dirname(__FILE__) + '/../lib/myproject' Where the project in question loaded ActiveRecord and, by implication, ActiveSupport, which doesn't actually load test/unit but defines the Test::Unit module. Therefore when Spec.exit? is called, it assumes test/unit has been loaded and calls Test::Unit.run?, resulting in the above error. Someone else had the same problem: https://www.ruby-forum.com/topic/155487 A workaround is to require 'spec' only after your app code has been initialized, so either Test will be there or it won't. This is the error that occurs: /var/lib/gems/1.8/gems/rspec-1.1.4/lib/spec.rb:27:in `exit?': undefined method `run?' for Test::Unit:Module (NoMethodError) from /var/lib/gems/1.8/gems/rspec-1.1.4/lib/spec/runner.rb:193:in `register_at_exit_hook' from spec/dsl_spec.rb:3 This doesn't happen on every machine, but it happens every time on my Ubuntu Linux 64-bit continuous integration machine when the following are true: 1) RSpec is loaded while Object.const_defined?(:Test) is false 2) Spec.exit? is called while Object.const_defined?(:Test) is true 3) test/unit has not been loaded My particular way to cause this was to have a spec_helper.rb file that looked like this: require 'rubygems' require 'spec' require File.dirname(__FILE__) + '/../lib/myproject' Where the project in question loaded ActiveRecord and, by implication, ActiveSupport, which doesn't actually load test/unit but defines the Test::Unit module. Therefore when Spec.exit? is called, it assumes test/unit has been loaded and calls Test::Unit.run?, resulting in the above error. Someone else had the same problem: https://www.ruby-forum.com/topic/155487 A workaround is to require 'spec' only after your app code has been initialized, so either Test will be there or it won't. <div><p>This is the error that occurs:</p> <p>/var/lib/gems/1.8/gems/rspec-1.1.4/lib/spec.rb:27:in <code>exit?': undefined method</code>run?' for Test::Unit:Module (NoMethodError)</p> <pre><code> from /var/lib/gems/1.8/gems/rspec-1.1.4/lib/spec/runner.rb:193:in `register_at_exit_hook' from spec/dsl_spec.rb:3 </code></pre> <p>This doesn't happen on every machine, but it happens every time on my Ubuntu Linux 64-bit continuous integration machine when the following are true:</p> <p>1) RSpec is loaded while Object.const_defined?(:Test) is false 2) Spec.exit? is called while Object.const_defined?(:Test) is true 3) test/unit has not been loaded</p> <p>My particular way to cause this was to have a spec_helper.rb file that looked like this:</p> <p>require 'rubygems' require 'spec'</p> <p>require File.dirname(<strong>FILE</strong>) + '/../lib/myproject'</p> <p>Where the project in question loaded ActiveRecord and, by implication, ActiveSupport, which doesn't actually load test/unit but defines the Test::Unit module. Therefore when Spec.exit? is called, it assumes test/unit has been loaded and calls Test::Unit.run?, resulting in the above error.</p> <p>Someone else had the same problem: <a href="https://www.ruby-forum.com/topic/155487">https://www.ruby-forum.com/topic...</a></p> <p>A workaround is to require 'spec' only after your app code has been initialized, so either Test will be there or it won't.</p></div> 1 This is the error that occurs: /var/lib/gems/1.8/gems/rspec-1.1.4/lib/spec.rb:27:in `exit?': undefined method `run?' for Test::Unit:Module (NoMethodError) from /var/lib/gems/1.8/gems/rspec-1.1.4/lib/spec/runner.rb:193:in `register_at_exit_hook' from spec/dsl_spec.rb:3 This doesn't happen on every machine, but it happens every time on my Ubuntu Linux 64-bit continuous integration machine when the following are true: 1. RSpec is loaded while `Object.const_defined?(:Test)` is `false` 2. `Spec.exit?` is called while `Object.const_defined?(:Test)` is `true` 3. `test/unit` has not been loaded My particular way to cause this was to have a spec_helper.rb file that looked like this: require 'rubygems' require 'spec' require File.dirname(__FILE__) + '/../lib/myproject' Where the project in question loaded ActiveRecord and, by implication, ActiveSupport, which doesn't actually load `test/unit` but defines the `Test::Unit` module. Therefore when `Spec.exit?` is called, it assumes `test/unit` has been loaded and calls `Test::Unit.run?`, resulting in the above error. Someone else had the same problem: https://www.ruby-forum.com/topic/155487 A workaround is to require 'spec' only after your app code has been initialized, so either `Test` will be there or it won't. My commit on github: http://github.com/eventualbuddha/rspec/commit/9dbeb477225dd877b437f4b2c4081de7794e30a7 <div><p>This is the error that occurs:</p> <pre><code>/var/lib/gems/1.8/gems/rspec-1.1.4/lib/spec.rb:27:in `exit?': undefined method `run?' for Test::Unit:Module (NoMethodError) from /var/lib/gems/1.8/gems/rspec-1.1.4/lib/spec/runner.rb:193:in `register_at_exit_hook' from spec/dsl_spec.rb:3 </code></pre> <p>This doesn't happen on every machine, but it happens every time on my Ubuntu Linux 64-bit continuous integration machine when the following are true:</p> <ol> <li>RSpec is loaded while <code>Object.const_defined?(:Test)</code> is <code>false</code></li> <li><code>Spec.exit?</code> is called while <code>Object.const_defined?(:Test)</code> is <code>true</code></li> <li><code>test/unit</code> has not been loaded</li> </ol> <p>My particular way to cause this was to have a spec_helper.rb file that looked like this:</p> <pre><code>require 'rubygems' require 'spec' require File.dirname(__FILE__) + '/../lib/myproject' </code></pre> <p>Where the project in question loaded ActiveRecord and, by implication, ActiveSupport, which doesn't actually load <code>test/unit</code> but defines the <code>Test::Unit</code> module. Therefore when <code>Spec.exit?</code> is called, it assumes <code>test/unit</code> has been loaded and calls <code>Test::Unit.run?</code>, resulting in the above error.</p> <p>Someone else had the same problem: <a href="https://www.ruby-forum.com/topic/155487">https://www.ruby-forum.com/topic...</a></p> <p>A workaround is to require 'spec' only after your app code has been initialized, so either <code>Test</code> will be there or it won't.</p> <p>My commit on github: <a href="http://github.com/eventualbuddha/rspec/commit/9dbeb477225dd877b437f4b2c4081de7794e30a7">http://github.com/eventualbuddha...</a></p></div> false 2008-08-22T19:14:08+02:00 24 --- {} 503 rspec-fails-to-finish-running-properly-depending-on-load-order 0 5645 new bug patch 2008-08-22T19:14:08+02:00 24 eventualbuddha eventualbuddha http://rspec.lighthouseapp.com/projects/5645/tickets/503 1 (from [7003e448de1d8ddcf31fc0198a8dd71a56e9ff70]) Check whether test/unit has really been loaded before calling a method it defines. [#503 state:resolved] http://github.com/dchelimsky/rspec/commit/7003e448de1d8ddcf31fc0198a8dd71a56e9ff70 <div><p>(from [7003e448de1d8ddcf31fc0198a8dd71a56e9ff70]) Check whether test/unit has really been loaded before calling a method it defines.</p> <p>[<a href="/projects/5645/tickets/503" title="Ticket #503">#503</a> state:resolved] <a href="http://github.com/dchelimsky/rspec/commit/7003e448de1d8ddcf31fc0198a8dd71a56e9ff70"> http://github.com/dchelimsky/rsp...</a></p></div> true 2008-11-28T17:34:00+01:00 24 --- :state: new 503 rspec-fails-to-finish-running-properly-depending-on-load-order 0 5645 resolved bug patch 2008-11-28T17:34:01+01:00 7315 David Chelimsky eventualbuddha http://rspec.lighthouseapp.com/projects/5645/tickets/503 7315 1 true 2008-11-28T17:34:15+01:00 24 --- :assigned_user: :milestone: 8417 21779 503 rspec-fails-to-finish-running-properly-depending-on-load-order 0 5645 resolved bug patch 2008-11-28T17:34:16+01:00 7315 David Chelimsky eventualbuddha David Chelimsky http://rspec.lighthouseapp.com/projects/5645/tickets/503 1.1.12 b0e398a29ab547fb6bbeb4423423d493ca15cdb0 text/plain 2008-08-22T19:12:23+02:00 really_check_for_test_unit.patch 40989 1707 24 http://rspec.lighthouseapp.com/attachments/40989/really_check_for_test_unit.patch