rake test fails with exit code 0 (Rails 3.2.0) #4923

Bastes opened this Issue Feb 7, 2012 · 10 comments


None yet

10 participants

Bastes commented Feb 7, 2012

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 :

  • create an empty new project
  • write a test that fails
  • rake test && echo "OK"
    => should show the test failing but still echoing OK after that
@Bastes Bastes closed this Feb 8, 2012
@Bastes Bastes reopened this Feb 8, 2012
Bastes commented Feb 8, 2012

(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

moeffju commented Feb 8, 2012

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.

salzig commented Feb 8, 2012

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.

jsl commented Feb 8, 2012
23tux commented Feb 27, 2012

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

rohit commented Mar 4, 2012

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.

kennyj commented Mar 4, 2012

I'm closing it. If we still have problem, please comment to this issue :)

@kennyj kennyj closed this Mar 4, 2012

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?

seuros commented Sep 22, 2014

Ask CruiseControl.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment