[issue3421] Test failure in test_math::testSum

Mark Dickinson added the comment: See also issue 5593. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue3421] Test failure in test_math::testSum

Raymond Hettinger <[EMAIL PROTECTED]> added the comment: The tests at floating point boundaries should probably be removed and their behavior should be left undefined. -- nosy: +rhettinger ___ Python tracker <[EMAIL PROTECTED]>

[issue3421] Test failure in test_math::testSum

Georg Brandl <[EMAIL PROTECTED]> added the comment: Strangely, it seems to work now with 3k too -- both in a debug and release build. I've no idea what changed, but I'll close this for now. -- resolution: -> works for me status: open -> closed ___ Py

[issue3421] Test failure in test_math::testSum

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Thanks. Those are the results I'd expect on x86. So here's the puzzle: On lines 658-9 of Lib/test/test_math.py, in revision 65248 of the py3k branch, there's a pair of lines that looks like: if 1e16+2.999 != 1e16+2.:

[issue3421] Test failure in test_math::testSum

Georg Brandl <[EMAIL PROTECTED]> added the comment: Both trunk and 3k give this: >>> 1e16 + 2. 10004.0 >>> 1.7976931348623157e+308 + 9.979201547673598e+291 inf ___ Python tracker <[EMAIL PROTECTED]> _

[issue3421] Test failure in test_math::testSum

Mark Dickinson <[EMAIL PROTECTED]> added the comment: See also issue 2819 for ongoing discussion, and issue 2937, which is the likely root cause of the current difficulties with math.sum. ___ Python tracker <[EMAIL PROTECTED]>

[issue3421] Test failure in test_math::testSum

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Sadly, this is not the only problem with math.sum on x86 hardware right now. I'd guess that this is another problem related to double-rounding and the use of 80-bit floating-point registers on x86. Raymond and I are still actively looking

[issue3421] Test failure in test_math::testSum

New submission from Georg Brandl <[EMAIL PROTECTED]>: In Py3k, but not in trunk: == FAIL: testSum (test.test_math.MathTests) -- Traceback (most recent call last