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

2.10: test error on big endian systems #16

Open
olebole opened this issue Dec 9, 2020 · 3 comments
Open

2.10: test error on big endian systems #16

olebole opened this issue Dec 9, 2020 · 3 comments

Comments

@olebole
Copy link

olebole commented Dec 9, 2020

The version 2.10 fails on one test when compiled on big endian systems like PowerPC 64 bit or IBM zSystems with :

FAIL: test_integration01.py
===========================


> WARNING: This executable has been compiled using a version of the ATLAS library without support for multithreading. Performance will be degraded.

sh: 1: convert: not found

> WARNING: FLAGS parameter not found in catalog GAIA-DR1_1334+3754_r46.cat


*** PLPLOT WARNING ***
Driver does not support hardware solid fills, switching to software fill.

Running Test #1 ...
SCAMP execution          ... passed
Minimum AS contrast: 44.1086 expected: > 22.00 ... passed
Minimum XY contrast: 48.8126 expected: > 22.90 ... passed
# of matched detections: 189983 expected: > 180100 ... passed
# of matched references: 2226 expected: > 1640 ... passed
Internal dispersion: 0.0354290517341998 expected: < 0.035 ... failed
Reference dispersion: 0.09366372231264102 expected: < 0.097 ... passed
1 errors.
FAIL test_integration01.py (exit status: 1)

Full build logs here for S390x (official Debian architecture), and here for PowerPC 64 bit (additional port).
I could ofcourse just adjust the limit for the internal dispersion, but I am afraid that this may hide a real problem.

@ebertin
Copy link
Member

ebertin commented Dec 9, 2020

Well actually all the numbers are different from the ones I get on x86 systems but I don't have presently direct access to a big-endian system. What would you suggest for me to have access to a big-endian system (outside of the Debian buildchain)? Thanks.

@olebole
Copy link
Author

olebole commented Dec 9, 2020

I have no good idea to to get you access. I can however access s390x directly myselt, if that would help.
Also, the issue is a regression and did not appear on 2.9.

@ebertin
Copy link
Member

ebertin commented Dec 9, 2020

OK, most likely a consequence of the change in the way endianity is handled then. Thanks, I'll take it from there.

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

No branches or pull requests

2 participants