2011-09-22 2 views
1
`--> rake test 
Coverage report generated for Unit Tests to /home/chris-kun/code/thirsty/coverage. 0/0 LOC (0.0%) covered. 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/rake_test_loader.rb:9: stack level too deep (SystemStackError) 
rake aborted! 
Command failed with status (1): [/usr/bin/ruby -I"lib:test" -I"/usr/lib/rub...] 

Tasks: TOP => test 
(See full trace by running task with --trace) 

위와 관련해서는 잘 모릅니다. 문제를 찾기 시작해야하는 곳은 어디입니까?rake_test_loader.rb - 스택 수준이 너무 높음

업데이트 : 그래서 단위 테스트를 위해 도우미 파일 내부에서 환경을로드하려고 시도 할 때 오류가 발생하는 것 같습니다. 스택 추적 :

`--> bundle exec rake test --trace 
** Invoke test (first_time) 
** Execute test 
** Invoke test:units (first_time) 
** Invoke test:prepare (first_time) 
** Execute test:prepare 
** Execute test:units 
** Invoke test:functionals (first_time) 
** Invoke test:prepare 
** Execute test:functionals 
** Invoke test:integration (first_time) 
** Invoke test:prepare 
** Execute test:integration 
/usr/lib/ruby/gems/1.9.1/gems/rest-open-uri-1.0.0/lib/rest-open-uri.rb:97: warning: already initialized constant Options 
/usr/lib/ruby/gems/1.9.1/gems/rest-open-uri-1.0.0/lib/rest-open-uri.rb:339: warning: already initialized constant StringMax 
/usr/lib/ruby/gems/1.9.1/gems/rest-open-uri-1.0.0/lib/rest-open-uri.rb:400: warning: already initialized constant RE_LWS 
/usr/lib/ruby/gems/1.9.1/gems/rest-open-uri-1.0.0/lib/rest-open-uri.rb:401: warning: already initialized constant RE_TOKEN 
/usr/lib/ruby/gems/1.9.1/gems/rest-open-uri-1.0.0/lib/rest-open-uri.rb:402: warning: already initialized constant RE_QUOTED_STRING 
/usr/lib/ruby/gems/1.9.1/gems/rest-open-uri-1.0.0/lib/rest-open-uri.rb:403: warning: already initialized constant RE_PARAMETERS 
Coverage report generated for Unit Tests to /home/chris-kun/code/thirsty/coverage. 0/0 LOC (0.0%) covered. 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/rake_test_loader.rb:9: stack level too deep (SystemStackError) 
rake aborted! 
Command failed with status (1): [/usr/bin/ruby -I"lib:test" -I"/usr/lib/rub...] 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/file_utils.rb:53:in `block in create_shell_runner' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/file_utils.rb:45:in `call' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/file_utils.rb:45:in `sh' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/file_utils_ext.rb:36:in `sh' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/file_utils.rb:80:in `ruby' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/file_utils_ext.rb:36:in `ruby' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/testtask.rb:99:in `block (2 levels) in define' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/file_utils_ext.rb:57:in `verbose' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/testtask.rb:98:in `block in define' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:205:in `call' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:205:in `block in execute' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:200:in `each' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:200:in `execute' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:158:in `block in invoke_with_call_chain' 
/usr/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:151:in `invoke_with_call_chain' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:144:in `invoke' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:112:in `invoke_task' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:90:in `block (2 levels) in top_level' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:90:in `each' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:90:in `block in top_level' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:129:in `standard_exception_handling' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:84:in `top_level' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:62:in `block in run' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:129:in `standard_exception_handling' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:59:in `run' 
/usr/lib/ruby/gems/1.9.1/gems/rake-0.9.2/bin/rake:32:in `<top (required)>' 
/usr/lib/ruby/gems/1.9.1/bin/rake:19:in `load' 
/usr/lib/ruby/gems/1.9.1/bin/rake:19:in `<main>' 
Tasks: TOP => test 
+0

루비의 버전은 무엇입니까? –

+0

실행 결과는 루비 1.9.1을 나타냅니다. –

+1

1.9.2 및 1.9.3은 보석에 대한 파일 경로에 1.9.1을 남겨 두었습니다. 따라서 우리 모두는> = 1.9.1입니다. –

답변

1

같은 일이 내게 일어난

UPDATE (https://github.com/thumblemonks/riot/issues/45 참조). 코드 적용 도구를 사용하고 있습니까? require은 어디에 두시겠습니까? 시험 파일의 맨 첫 줄에 있습니까?

+0

에서 같은 동작을보고 있는데 문제는 제거 할 때도 계속 나타납니다. –

+0

어떤 코드 적용 도구입니까? 'require' 문은 어디에 넣었습니까? –

+0

나는 simplecov를 사용하고 teststrap.rb 파일의 맨 위에 require 문을 두었습니다. 그러나 simplecov가 제거 될 때도 문제가 여전히 발생한다고 말했기 때문에 관련성이없는 것으로 보입니다. –

관련 문제