Skip to content
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

1.2RC1 test_identity fails on arm64, powerpc, ppc64, ppc64el, s390x #5096

Closed
olebole opened this issue Jun 15, 2016 · 4 comments
Closed

1.2RC1 test_identity fails on arm64, powerpc, ppc64, ppc64el, s390x #5096

olebole opened this issue Jun 15, 2016 · 4 comments

Comments

@olebole
Copy link
Member

olebole commented Jun 15, 2016

This is an issue in the same function as #3486; however with a different output. It was hidden for a while since I had to skip wcs doctests due to #3380.

_________________ [doctest] astropy.wcs.wcs.WCS.all_world2pix __________________
2102         ...   print("Best solution:\\n{{0}}".format(e.best_solution))
2103         ...   print("Achieved accuracy:\\n{{0}}".format(e.accuracy))
2104         Indices of diverging points: [1]
2105         Indices of poorly converging points: None
2106         Best solution:
2107         [[  1.00000238e+00   9.99999965e-01]
2108          [ -1.99441636e+06   1.44309097e+06]
2109          [  3.00000236e+00   9.99999966e-01]]
2110         Achieved accuracy:
2111         [[  6.13968380e-05   8.59638593e-07]
Differences (unified diff with -expected +actual):
    @@ -6,5 +6,5 @@
      [  3.00000236e+00   9.99999966e-01]]
     Achieved accuracy:
    -[[  6.13968380e-05   8.59638593e-07]
    +[[  6.13968380e-05   8.59638595e-07]
      [  8.59526812e+11   6.61713548e+11]
    - [  6.09398446e-05   8.38759724e-07]]
    + [  6.09398446e-05   8.38759723e-07]]

astropy/wcs/wcs.py:2111: DocTestFailure
@astrofrog
Copy link
Member

astrofrog commented Jun 15, 2016

This should be fixed in #5080 - I'll mark this as 'Close?' to remind us it's probably solved.

@astrofrog
Copy link
Member

@olebole - can you confirm this is fixed in the latest stable release?

@olebole
Copy link
Member Author

olebole commented Jul 5, 2016

Yes, this does not appear anymore and can be closed.

@astrofrog
Copy link
Member

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants