can't run actionpack tests directly due to errant require

Bummer. I just followed my instructions above (starting with a clean clone) and got the same result.

Any chance you've got active_support's lib directory on your path? That could explain why you don't get this error.

I do have the gems installed. Maybe that's it? Do you not have any Rails gems installed?

I do:

actionmailer (2.1.1, 2.1.0, 1.3.6) actionpack (2.1.1, 2.1.0, 1.13.6) actionwebservice (1.2.6) activerecord (2.1.1, 2.1.0, 1.15.6) activeresource (2.1.1, 2.1.0) activesupport (2.1.1, 2.1.0, 1.4.4) rails (2.1.1, 2.1.0, 1.2.6)

So that's probably not it by itself. I was thinking more like you just had it added to your PATH in your .profile or .bash_login or whatever you might be using.

Could also be a fluke of load order - I see, for example, in lib/action_controller.rb:

begin
  require 'active_support'
rescue LoadError
  activesupport_path = "#{File.dirname(__FILE__)}/../../activesupport/lib"
  if File.directory?(activesupport_path)
    $:.unshift activesupport_path
    require 'active_support'
  end
end

So if that file gets loaded before lib/action_controller/request.rb (which is the source of the load error I'm getting when it tries to require 'active_support/memoizable'), you wouldn't see the error I'm seeing

Can you delete line 2 of test/abstract_unit and still run the tests? That would support this load order theory.

We are also seeing the above issue on our local builds of Rails.

Can David's fix above be applied? It looks like it maintains the exact behavior and fixes the load order issue.

I've been seeing this one as well.

Patch attached that incorporates David Chelimsky's fix, and a similar fix for http://rails.lighthouseapp.com/p... , which has the same root cause.