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

Test failure on i686 #570

Closed
mbakke opened this issue Sep 25, 2019 · 5 comments
Closed

Test failure on i686 #570

mbakke opened this issue Sep 25, 2019 · 5 comments
Milestone

Comments

@mbakke
Copy link

mbakke commented Sep 25, 2019

Hello,

Running the OpenEXR 2.4.0 test suite on 32-bit x86 Linux yields this failure:

=======
Running testLargeDataWindowOffsets
Testing dataWindows with large offsets ... 
dataWindow: (28701996 205844709) (28702591 205845061) 
dataWindow: (-485824597 504726626) (-485824166 504727112)  OK 
dataWindow: (-150831402 288082664) (-150830931 288083109) 
dataWindow: (122833846 -93407155) (122835173 -93406997) 
dataWindow: (-53467928 -490674469) (-53467515 -490673962) 
dataWindow: (-358470157 426600481) (-358465598 426600527) 

error reading back channel B pixel -358469942,426600481 got -nan expected -nan
@peterhillman
Copy link
Contributor

Would it be possible to re-test this against master? The newly merged fix for #571 may also address this issue if 32-bit x86 processors also fail to read non-aligned floats correctly.

@mbakke
Copy link
Author

mbakke commented Nov 7, 2019

peterhillman added a commit to peterhillman/openexr that referenced this issue Nov 28, 2019
cary-ilm pushed a commit that referenced this issue Jan 24, 2020
@peterhillman
Copy link
Contributor

@mbakke, could you possibly retest against the latest master to see if fce8c17 has fixed the issue? I don't have easy access to 32 bit x86 linux to test or debug the issue

@mbakke
Copy link
Author

mbakke commented Jan 29, 2020

@peterhillman I can confirm that this test no longer fails on 32-bit x86 (on commit 6546ff2). 🎉

@peterhillman
Copy link
Contributor

Great! I'll call that fixed and close the ticket

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

3 participants