This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zach.ware
Recipients rhettinger, serhiy.storchaka, zach.ware
Date 2013-11-14.20:34:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384461288.76.0.822218822712.issue19588@psf.upfronthosting.co.za>
In-reply-to
Content
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?
History
Date User Action Args
2013-11-14 20:34:48zach.waresetrecipients: + zach.ware, rhettinger, serhiy.storchaka
2013-11-14 20:34:48zach.waresetmessageid: <1384461288.76.0.822218822712.issue19588@psf.upfronthosting.co.za>
2013-11-14 20:34:48zach.warelinkissue19588 messages
2013-11-14 20:34:48zach.warecreate