New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.6.2c1 fails to pass test_cmath on Solaris10 #49974
Comments
I configured and built Python 2.6.2c1 on Solaris 10 using gcc 4.2.
test_cmath
Traceback (most recent call last):
File "/home/tuba/skipm/src/Python-2.6.2c1/Lib/test/test_cmath.py",
line 338, in test_specific_values
self.fail('OverflowError not raised in test %s' % test_str)
AssertionError: OverflowError not raised in test exp0052:
exp(complex(710.0, 1.5))
FAILED (failures=1)
test test_cmath failed -- Traceback (most recent call last):
File "/home/tuba/skipm/src/Python-2.6.2c1/Lib/test/test_cmath.py",
line 338, in test_specific_values
self.fail('OverflowError not raised in test %s' % test_str)
AssertionError: OverflowError not raised in test exp0052:
exp(complex(710.0, 1.5))
Since we are so close to release I'm assigning it to Barry, though |
I'll mark this as a release blocker for 2.6.2 for now, until Mark weighs in. |
Sorry for the late reply: I've been away for a few days. This looks like the same problem as bpo-4575, so |
Here's a patch that backports the corresponding changes from trunk. Skip, can you confirm that this fixes the issue? |
Just to say, I'm a bit uncomfortable with a patch this large going into a The test failure that Skip reports *is* due to a bug, but the bug is I don't think the (small, I hope) risk of breaking a release candidate is Assigning back to Barry for pronouncement. |
Mark> Here's a patch that backports the corresponding changes from
Indeed, your patch appears to fix the problem:
I'll leave it to you and Barry to consider if the patch is too hefty for Skip |
FWIW, with the patch applied all tests still pass on Mac OS X 10.5.6 S |
We'll omit this for 2.6.2. Mark, please feel free to apply it once |
Accepted for 2.6.3. |
Applied in r72275. I've also applied the same changes to the |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: