Added backwards incompatibility note to 1.1.2 release notes for the change in test runner exit status codes (refs #11615).

git-svn-id: http://code.djangoproject.com/svn/django/trunk@12070 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Gary Wilson Jr 2010-01-03 19:02:55 +00:00
parent 5dd6bbd2cf
commit 28d2d3e705
1 changed files with 14 additions and 1 deletions

View File

@ -19,8 +19,21 @@ development or deployment currently using or targeting Django 1.1.
For full details on the new features, backwards incompatibilities, and For full details on the new features, backwards incompatibilities, and
deprecated features in the 1.1 branch, see the :ref:`releases-1.1`. deprecated features in the 1.1 branch, see the :ref:`releases-1.1`.
Backwards-incompatible changes in 1.1.2
=======================================
Test runner exit status code
----------------------------
The exit status code of the test runners (``tests/runtests.py`` and ``python
manage.py test``) no longer represents the number of failed tests, since a
failure of 256 or more tests resulted in a wrong exit status code. The exit
status code for the test runner is now 0 for success (no failing tests) and 1
for any number of test failures. If needed, the number of test failures can be
found at the end of the test runner's output.
One new feature One new feature
--------------- ===============
Ordinarily, a point release would not include new features, but in the Ordinarily, a point release would not include new features, but in the
case of Django 1.1.2, we have made an exception to this rule. Django case of Django 1.1.2, we have made an exception to this rule. Django