# Strange Exception when running rake test

**URL:** <https://www.ruby-forum.com/t/strange-exception-when-running-rake-test/115521>\
**Category:** Rails\
**Created:** [September 25, 2007, 11:31pm UTC](https://www.ruby-forum.com/t/strange-exception-when-running-rake-test/115521 "2007-09-25T23:31:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![unknown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/4bbf92/32.png) [@unknown](https://www.ruby-forum.com/u/unknown)\
**Post date:** [September 25, 2007, 11:31pm UTC](https://www.ruby-forum.com/t/strange-exception-when-running-rake-test/115521/1 "2007-09-25T23:31:27Z")

</div>

I get the following exception sometimes when I run rake test and I  
have some failures/errors in my test cases. It occurs after units/  
functionals/integration complete.

Command failed with status (1): [/usr/bin/ruby18 -Ilib:test "/usr/  
lib64/rub…]  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:719:in `sh' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:726:in`call’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:726:in `sh' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:805:in`sh’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:740:in `ruby' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:805:in`ruby’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake/testtask.rb:117:in  
`define' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:823:in`verbose’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake/testtask.rb:102:in  
`define' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in`call’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in`each’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:362:in`invoke’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in  
`synchronize' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in`invoke’  
/usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/tasks/testing.rake:45  
/usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/tasks/testing.rake:43:in  
`collect' /usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/tasks/testing.rake:43 /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in`call’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in`each’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:362:in`invoke’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in  
`synchronize' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in`invoke’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in  
`top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in`each’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in  
`top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in`standard\_exception\_handling’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1733:in  
`top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1711:in`run’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in  
`standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1708:in`run’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/bin/rake:7  
/usr/bin/rake:16:in `load' /usr/bin/rake:16 rake aborted! Test failures /usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/tasks/testing.rake:53 /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in`call’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in`each’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:392:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:362:in`invoke’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in  
`synchronize' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:355:in`invoke’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in  
`top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in`each’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1739:in  
`top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in`standard\_exception\_handling’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1733:in  
`top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1711:in`run’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in  
`standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1708:in`run’  
/usr/lib64/ruby/gems/1.8/gems/rake-0.7.3/bin/rake:7  
/usr/bin/rake:16:in `load’  
/usr/bin/rake:16

I am running ruby 1.8.6 (2007-06-07 patchlevel 36) [x86\_64-linux] and  
rails 1.2.3, rake 0.7.3

Any ideas? It is just an annoyance because it turns the return code  
of rake test to be non zero.

Thanks,  
Curtis

---

<div class="post-metadata">

**Author:** ![unknown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/4bbf92/32.png) [@unknown](https://www.ruby-forum.com/u/unknown)\
**Post date:** [September 26, 2007, 4:51am UTC](https://www.ruby-forum.com/t/strange-exception-when-running-rake-test/115521/2 "2007-09-26T04:51:17Z")

</div>

I don’t understand - you get the stacktrace below when some of your  
tests fail or error? That’s the proper behavior.