New submission from Zachary Ware:
See: http://hg.python.org/cpython/file/87099/Lib/test/test_random.py#l241
This test (and its match in MersenneTwister_TestBasicOps) is nearly always
skipped by the 'if stop <= start: return' check; in a test with adding
"print('skipped', i)" before the return and running test_random via regrtest
with -F, i was 40 when the test returned about 21 out of 25 times. It seems to
have been this way since the test was added.
Was this intended? It looks to me like perhaps the start and stop assignments
are swapped; Serhiy suggested that perhaps stop was meant to have been added to
start. How is this test meant to work?
----------
components: Tests
messages: 202879
nosy: rhettinger, serhiy.storchaka, zach.ware
priority: normal
severity: normal
status: open
title: Silently skipped test in test_random
type: behavior
versions: Python 2.7, Python 3.3, Python 3.4
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue19588>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
