rspec users - May 2011 - Upgrading to rspec-rails version 2.6 causes 'stack level too deep' SystemStackError

Has anyone else had this problem?  Everything was working well with 
rspec-rails 2.5.0.  I gem updated to 2.6.0 and now I get the error:

rspec-core-2.6.1/lib/rspec/core/configuration.rb:419: stack level too deep 
(SystemStackError)


This is where it is attempting to load the files.

My file structure is standard, but I do have some shared examples in 
spec/support/shared_examples.  This worked with 2.5.0

I hope someone has a quick ''have you tried...''


-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/rspec-users/attachments/20110519/0f81b4e2/attachment.html>

On 2011-05-19 6:17 PM, Brad wrote:
> Has anyone else had this problem?  Everything was working well with 
> rspec-rails 2.5.0.  I gem updated to 2.6.0 and now I get the error:
>
>     rspec-core-2.6.1/lib/rspec/core/configuration.rb:419: stack level
>     too deep (SystemStackError)
>
>
> This is where it is attempting to load the files.
>
> My file structure is standard, but I do have some shared examples in 
> spec/support/shared_examples.  This worked with 2.5.0
>
> I hope someone has a quick ''have you tried...''
>
>
I had a similar problem, but with rspec 1.3.2 and rspec-rails 1.3.4 when 
I upgraded from ruby 1.8.7 to 1.9.2. I tried my best to step through 
everything involved, but never really could figure it out. As I was 
debugging, I had cause to want files to be loaded in the same order 
every time so I could see if one of my files had a problem. I ended up 
taking

--loadby mtime
--reverse

out of spec/spec.opts, and the problem went away. This is the thread

http://groups.google.com/group/rspec/browse_thread/thread/8b655aaf3ad07f04?hl=en

Phillip