bpo-38992: avoid fsum test failure from constant-folding (GH-17513)

* Issue 38992: avoid fsum test failure

* Add NEWS entry
This commit is contained in:
Mark Dickinson 2019-12-09 08:36:34 -06:00 committed by GitHub
parent ab513a38c9
commit bba873e633
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 1 deletions

View File

@ -676,7 +676,6 @@ class MathTests(unittest.TestCase):
float.fromhex('0x1.df11f45f4e61ap+2')),
([(-1.)**n/n for n in range(1, 1001)],
float.fromhex('-0x1.62a2af1bd3624p-1')),
([1.7**(i+1)-1.7**i for i in range(1000)] + [-1.7**1000], -1.0),
([1e16, 1., 1e-16], 10000000000000002.0),
([1e16-2., 1.-2.**-53, -(1e16-2.), -(1.-2.**-53)], 0.0),
# exercise code for resizing partials array
@ -685,6 +684,13 @@ class MathTests(unittest.TestCase):
float.fromhex('0x1.5555555555555p+970')),
]
# Telescoping sum, with exact differences (due to Sterbenz)
terms = [1.7**i for i in range(1001)]
test_values.append((
[terms[i+1] - terms[i] for i in range(1000)] + [-terms[1000]],
-terms[0]
))
for i, (vals, expected) in enumerate(test_values):
try:
actual = math.fsum(vals)

View File

@ -0,0 +1 @@
Fix a test for :func:`math.fsum` that was failing due to constant folding.