Message305391
| Author |
skrah |
| Recipients |
davin, jeff.allen, mark.dickinson, rhettinger, serhiy.storchaka, skrah, tim.peters |
| Date |
2017年11月01日.18:47:11 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<20171101184700.GA10587@bytereef.org> |
| In-reply-to |
<1509560264.41.0.213398074469.issue31630@psf.upfronthosting.co.za> |
| Content |
On Wed, Nov 01, 2017 at 06:17:44PM +0000, Mark Dickinson wrote:
> I'm really reluctant to (even conditionally) skip the test, because it's doing exactly what it's designed to do, namely detecting and reporting that Python is giving poor results in this corner case on this platform. As developers, we can blame the poor results on the platform's libm, but that doesn't help the user.
I would want the tests to fail, especially if it can occur on Linux (though I
still suspect an i686 router in the reported case).
Perhaps hide them behind -uall, so that *we* see the result but just
executing ./python -m test passes. |
|