Hi, we've been noticing that Rails 3.2.0 fails its tests returning the exit code 0 (which makes it hard for a continuous integration tool to know when the build is broken).
How to reproduce :
(sorry for closing earlier, I tried to reproduce on a 3.0.10 instead of a 3.2.0 by mistake)
Fails with 3.2.0 for sure (just tested).
Another symptom : no "Errors running test:units!" at the end of rake's output
I just ran into this same issue. rake test returns 0, even if errors occurred. Rails 3.2.1 on Ruby 1.9.3-p0.
Same here. (ruby 1.9.2p290, Rails 3.2.1)
I can reproduce this as well. Ruby 1.9.2-p290, Rails 3.2.1.
Looks like this may have been fixed in http://github.com/rails/rails/commit/abe4a8d070d069f24f7befd9a8da25c40f4c2a6d.
Having the same behaviour, Ruby 1.9.3-p0, Rails 3.2.1. Change to Rails 3.2.2.rc1 will fix this bug, or wait for 3.2.2 stable
Since Rails 3.2.2 has already been released and this issue is fixed according to that commit, @23tux can you please close this issue.
I'm closing it. If we still have problem, please comment to this issue :)
Hey! can you guys tell me how can I get the exit code from custom build task in CruiseControl, check the exit code to do certain task like deployment using capistrano?