RetroSearch Browse

Wed Jul 20 20:48:18 CEST 2011 · https://mail.python.org/pipermail/python-dev/2011-July/112379.html

On 7/20/2011 12:25 PM, Victor Stinner wrote:
> Le 20/07/2011 17:58, Éric Araujo a écrit :
>> Do we have a policy of not adding new test files to stable branches?
> New logging tests failed during some weeks. If we add new tests, we may
> also break some stable buildbots. I don't think that we need to add
> these new tests to a stable version.

When bugs are fixed in stable branches, they are usually accompanied by 
tests that fail without the bugfix. I have understood the policy to be 
that new tests go into stable branches. Failure indicates a bug in 
either the not-really-so-stable branch or the test. In the latter case, 
remove the test everywhere until fixed. In the former case, either fix 
the bug in the stable branch immediately or open an issue and attach the 
test code (skipping the test needed stage) or just disable it and note 
on the issue that a fix patch should re-enable. The logging tests may 
have been exceptional some way.

-- 
Terry Jan Reedy

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-July/112379.html below:

[Python-Dev] New tests in stable versions