-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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: TestFilePng.test_save_p_transparent_black #3243
Comments
If it helps, I was able to pass test_file_png tests in 64-bit Gentoo in Python 2.7. |
Mips64el (little endian) is same.
Maybe, is it a python bug ? |
Interestingly, big endian is now part of our CI jobs (#4336), and this test passes. |
This is what I get with 7.0.0 on Gentoo Sparc:
|
Failures on ppc64 (big endian), Gentoo:
|
Updated error list for Pillow 7.2.0 on Gentoo/Sparc (tl;dr: the same as on ppc64 above): platform linux -- Python 3.7.8, pytest-4.6.11, py-1.8.0, pluggy-0.13.1 -- /usr/bin/python3.7
|
I get exactly the same test failures on hppa with 7.2.0 as on sparc, with the same value differences. |
Because it magically passes there. Found it passing in the logs of 6.2.1, 6.2.2, 7.2.0, and 8.0.1. |
I expect the failures listed in #3243 (comment), #3243 (comment) and #3243 (comment) to now be passing on main (thanks to #5364, #5901 and #4457), leaving just |
If @DerDakon is saying that |
If the test_save_p_transparent_black problem is purely a big endian issue, then I'm unable to reproduce it with Pillow 5.1.0 - radarhere/docker-images@50f2964 passes in https://github.com/radarhere/docker-images/runs/4679158046 |
Pillow 9.0 has been released. So everything except for |
On hppa all tests pass. On sparc I had only one unrelated error:
Can be hard to meet such short timing requirements if it involves disk I/O, e.g. for start of external programs. |
When I run the testsuite on my Gentoo HPPA (big endian!) machine, I get this:
This can be traced back to at least 3.4.2, as reported in this downstream bug. After fixing the SIGBUS errors on 4.3.0 I had the same problem on sparc, so it may be a big endian issue.
The text was updated successfully, but these errors were encountered: