Just updated to 2.2, and our deploy script is broken, because cache:clear returns with exit status 0, even if the clearing fails. Previously, it returned with status 1 if the clearing failed. Is this the new expected behavior?

Reproducing:

Check out Symfony 2.2.1
Make a deliberate error in your configuration
run php app/console cache:clear; echo $? // outputs 1

Check out Symfony 2.2.2
Make a deliberate error in your configuration
run php app/console cache:clear; echo $? // outputs 0

Throwing an exception in a console command results in exit status 0 in 2.2, but results in 1 in 2.1, which probably means all console commands are affected, not just the cache:clear. This leads to a very bad situation, where deploy tools, like Capistrano will report that everything went fine, when in reality, the deploy failed.

Stelian1 in the IRC channel mentioned that this might be related to the pull request #5476. Also according to him, the downloaded 2.2 with vendors version works fine, so maybe only the without-vendors version is affected.