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 martin.panter
Recipients berker.peksag, martin.panter, rhettinger, serhiy.storchaka, vstinner
Date 2016-10-21.00:51:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1477011091.29.0.32843262498.issue26163@psf.upfronthosting.co.za>
In-reply-to
Content
I just got this failure again today. I think I have seen it once or twice before. Is the failure actually indicating a problem with Python, or is the test just too strict?

It seems that it may be like a test ensuring that a random.randint(1, 100) is never equal to 81: the probability of it failing is low, but not close enough to zero to rely on it never failing. On the other hand, a test ensuring that a 512-bit cryptographic hash doesn’t collide might be valid because the probability is low enough.
History
Date User Action Args
2016-10-21 00:51:31martin.pantersetrecipients: + martin.panter, rhettinger, vstinner, berker.peksag, serhiy.storchaka
2016-10-21 00:51:31martin.pantersetmessageid: <1477011091.29.0.32843262498.issue26163@psf.upfronthosting.co.za>
2016-10-21 00:51:31martin.panterlinkissue26163 messages
2016-10-21 00:51:29martin.pantercreate