Message202879
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? |
|
Date |
User |
Action |
Args |
2013-11-14 20:34:48 | zach.ware | set | recipients:
+ zach.ware, rhettinger, serhiy.storchaka |
2013-11-14 20:34:48 | zach.ware | set | messageid: <1384461288.76.0.822218822712.issue19588@psf.upfronthosting.co.za> |
2013-11-14 20:34:48 | zach.ware | link | issue19588 messages |
2013-11-14 20:34:48 | zach.ware | create | |
|