Meador Inge <mead...@gmail.com> added the comment:
On Sun, Aug 14, 2011 at 1:03 PM, Stefan Krah <rep...@bugs.python.org> wrote:
>
> Stefan Krah <stefan-use...@bytereef.org> added the comment:
>
> I like random tests in the stdlib, otherwise the same thing gets tested
> over and over again. `make buildbottest` prints the seed, and you can do
> it for a single test as well:
>
> $ ./python -m test -r test_heapq
> Using random seed 5857004
> [1/1] test_heapq
> 1 test OK.
Ah, I see. Then you can reproduce a run like:
$ ./python -m test -r --randseed=5857004 test_heapq
Perhaps it might be useful to include the failing output in the
assertion message as well
(just in case the seed printing option is not used):
======================================================================
FAIL: test_Struct_nmemb (__main__.StructTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "Lib/test/test_struct.py", line 596, in test_Struct_nmemb
self.assertEqual(s.nmemb, n, "for struct.Struct(%s)" % fmt)
AssertionError: 3658572 != 3658573 : for
struct.Struct(378576l?403320c266165pb992937H198961PiIL529090sfh887898d796871B)
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue12740>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
