test: Changelog

Mercurial Mercurial > test / changelog

Sun, 10 Feb 2013 01:51:28 +0000 Merge with stable

changeset

Christian Ebert <blacktrash@gmx.net> [Sun, 10 Feb 2013 01:51:28 +0000] rev 1213

Merge with stable

Wed, 30 Jan 2013 01:24:04 +0100 test: display used python hash seed stable

changeset

Pierre-Yves David <pierre-yves.david@ens-lyon.org> [Wed, 30 Jan 2013 01:24:04 +0100] rev 1212

test: display used python hash seed We keep using a random seed for each run, but we "compute" it ourself to be able to reproduce a failed test run. [ original upstream message ]

Fri, 08 Feb 2013 12:11:51 +0000 Merge with stable

changeset

Christian Ebert <blacktrash@gmx.net> [Fri, 08 Feb 2013 12:11:51 +0000] rev 1211

Merge with stable

Wed, 24 Oct 2012 23:09:31 +0200 run-tests: do not fail on empty tsttest file stable

changeset

Simon Heimberg <simohe@besonet.ch> [Wed, 24 Oct 2012 23:09:31 +0200] rev 1210

run-tests: do not fail on empty tsttest file Initialize n for not failing on empty tsttest files. [ original upstream message ]

Tue, 29 Jan 2013 22:19:10 +0000 Merge with stable

changeset

Christian Ebert <blacktrash@gmx.net> [Tue, 29 Jan 2013 22:19:10 +0000] rev 1209

Merge with stable

Tue, 29 Jan 2013 20:03:51 +0100 run-tests.py: inherit PYTHONHASHSEED from environment if set stable

changeset

Mads Kiilerich <madski@unity3d.com> [Tue, 29 Jan 2013 20:03:51 +0100] rev 1208

run-tests.py: inherit PYTHONHASHSEED from environment if set This makes it possible to fix the seed by using for instance PYTHONHASHSEED=7 ./run-tests.py ... This can be very convenient when trying to debug problems that are influenced by hash values. Try different seed values until you find one that triggers the bad behaviour and then keep that while debugging. The value 0 will restore default Python behavior and disable randomization. [ original upstream message ]

(0) -1000 -300 -100 -30 -10 -6 +6 +10 +30 +100 tip

test

RSS Atom