rspec stack level too deep

Question

When I run my model specs and controller specs separately, it's fine. When I run them together, I get a stack overflow, literally :)

$ bundle exec rspec --fail-fast spec/models
........

Finished in 0.44274 seconds
8 examples, 0 failures

$ bundle exec rspec --fail-fast spec/controllers
..

Finished in 0.99339 seconds
2 examples, 0 failures

$ bundle exec rspec --fail-fast spec
F

Failures:

  1) HerpController derp derp example
     Failure/Error: Unable to find matching line from backtrace
     SystemStackError:
       stack level too deep
     # /Users/jared/.rvm/gems/ruby-1.9.2-p290/gems/actionpack-3.2.1/lib/abstract_controller/layouts.rb:359

Finished in 0.02241 seconds
1 example, 1 failure

How do I even begin to debug this? Thanks.

I'd remove half your controller/model specs at random and see if it the problem remains. If it does, remove some more controller specs. If it doesn't then restore the specs you removed and remove the ones that were initially left in place. Repeat until you've narrowed it down to a specific set of specs — Frederick Cheung, Feb 12 '12 at 15:16

Jared Beck · Accepted Answer · 2012-02-13T05:20:49.323

11

Removing half of my specs at a time turned up the problem. I suppose this is an example of bisect debugging. Thanks to Frederick Cheung, whose comment suggested this approach.

For posterity, this was the problem.

include Rails.application.routes.url_helpers
describe "Attendee#next_page" do
end

Apparently, includes go inside the describe

describe "Attendee#next_page" do 
  include Rails.application.routes.url_helpers
end

I have a lot to learn about rspec. :)

edited Feb 13 '12 at 05:20

answered Feb 13 '12 at 05:11

Jared Beck

16,796
9
72
97

For those looking to pursue the bisect debugging approach you may find `rspec --bisect` helpful: https://relishapp.com/rspec/rspec-core/docs/command-line/bisect – Charlie Weems Feb 20 '18 at 06:24

score 1 · Answer 2 · answered Feb 12 '12 at 07:40

1

You can either put a debugger statement in your code and debug that way, or just start using puts "got here" in the places of your code that you know are being run. I would suggest using something meaningful instead of "got here" too :-)

answered Feb 12 '12 at 07:40

siannopollo

1,464
11
24

This `puts` technique is what I use too, and I have to say it's got to be the most underrated way of debugging ever! – Marco Prins Jun 10 '14 at 12:34

score 0 · Answer 3 · answered Jul 30 '13 at 11:50

Possibly you can get "Unable to find matching line from backtrace" error in case you are checking some var which wasn't initialised actually

In this example pay attention to var observation which is not initialised in the wrong snippet

wrong snippet

describe "GET index" do
  it "assigns all observations as @observations" do
    get :index, {}, valid_session
    assigns(:observations).should eq([observation])
  end
end

fixed example (line 3)

describe "GET index" do
  it "assigns all observations as @observations" do
    observation = Observation.create! valid_attributes
    get :index, {}, valid_session
    assigns(:observations).should eq([observation])
  end
end

Sometimes we rely on using let as initializer, but forget to add it e.g.

let(:observation) {FactoryGirl.create(:observation)}

score 0 · Answer 4 · answered Feb 12 '12 at 10:30

I'd start either with puts or raise statements at key points in your code so you can start to narrow down which line is causing the problem. Once you start getting close, you can comment out one line at a time to figure out which line the problem disappears with - as soon as you've got it down to one line, you can figure out what that line is doing that Ruby doesn't like.

In general terms of where to start, "Stack level too deep" is usually an infinite loop or infinite recursion problem - I'd imagine that there's something going on where a model is invoking a controller that's invoking the model, or vice-versa. No way to know for sure until you start commenting out lines, but any place where you've got function calls is going to belong on your suspect short list. Good luck!

rspec stack level too deep

4 Answers4

Linked