Created attachment 1863861 [details] Build log with test failure details Description of problem: Multiple tests fail on s390x. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. fedpkg scratch-build --arches s390x Actual results: Success, as on other architectures Expected results: FAILED tests/test_tiff2jp2.py::TestSuite::test_minisblack_3strip_to_2x2 - Zer... FAILED tests/test_tiff2jp2.py::TestSuite::test_partial_last_strip - ZeroDivis... FAILED tests/test_tiff2jp2.py::TestSuite::test_partial_strip_and_partial_tiles FAILED tests/test_tiff2jp2.py::TestSuite::test_psnr - AssertionError: False i... FAILED tests/test_tiff2jp2.py::TestSuiteNoScikitImage::test_rgb_stripped - Ze... FAILED tests/test_tiff2jp2.py::TestSuiteNoScikitImage::test_rgb_stripped_bottom_of_tile_coincides_with_bottom_of_strip FAILED tests/test_tiff2jp2.py::TestSuiteNoScikitImage::test_stripped_logging Additional info: See attached build log, which assumes https://src.fedoraproject.org/rpms/python-glymur/pull-request/1 has been merged. Since s390x is the only big-endian architecture in Fedora, one can assume that endianness-related issues are a likely cause. It’s not obvious whether the problem is in glymur or in openjpeg2, although I would guess glymur is more likely.
It looks like these failures are new in 0.9.7 vs. 0.9.4. They are all for the new tiff2jp2 tool.
I’ve figured out what’s going on here: https://github.com/quintusdias/glymur/issues/545
Upstream has promised to work on this. Most of the tests that fail are due to a real bug that could affect TIFF images with RowsPerStrip>65535 on any platform, but is much worse on big-endian platforms. The “psnr” test fails for a different reason that I haven’t looked into yet. If upstream doesn’t fix it together with the main bug, I’ll report it separately. Given all that, I think it’s OK to go ahead and skip the failing tests on s390x and package 0.9.8 to resolve bug 2060033 and bug 2062941. I’ll update https://src.fedoraproject.org/rpms/python-glymur/pull-request/1 to do that.
oh I see this is assigned to me?
As the one who requested the dist-git repo, you’re the package owner / main admin, so you’re the default bug assignee, and bugfixes/updates are generally up to you unless someone else notices and steps up. That said, I think I meant to assign this to myself when I changed the status to ASSIGNED. I’ve merged [1] with a workaround to skip the failing tests, and for now this issue is in upstream’s hands to fix. I’m subscribed to the upstream bug[2], so I should notice when upstream offers a fix and follow up here. As the main admin for this package, you might want to subscribe to the upstream bug, too. [1] https://src.fedoraproject.org/rpms/python-glymur/pull-request/2 [2] https://github.com/quintusdias/glymur/issues/545
(In reply to Ben Beasley from comment #5) > As the one who requested the dist-git repo, you’re the package owner / main > admin, so you’re the default bug assignee, and bugfixes/updates are > generally up to you unless someone else notices and steps up. > > That said, I think I meant to assign this to myself when I changed the > status to ASSIGNED. I’ve merged [1] with a workaround to skip the failing > tests, and for now this issue is in upstream’s hands to fix. I’m subscribed > to the upstream bug[2], so I should notice when upstream offers a fix and > follow up here. As the main admin for this package, you might want to > subscribe to the upstream bug, too. > > [1] https://src.fedoraproject.org/rpms/python-glymur/pull-request/2 > [2] https://github.com/quintusdias/glymur/issues/545 Alright, thank you.
FEDORA-2022-63d37b251a has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-63d37b251a
FEDORA-2022-63d37b251a has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-43a14f9ff4 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-43a14f9ff4
FEDORA-2022-4d2547f6fc has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-4d2547f6fc
FEDORA-2022-bc8c250ccd has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-bc8c250ccd
FEDORA-2022-43a14f9ff4 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-43a14f9ff4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-43a14f9ff4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-bc8c250ccd has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-bc8c250ccd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-bc8c250ccd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-4d2547f6fc has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-4d2547f6fc` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-4d2547f6fc See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-43a14f9ff4 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-4d2547f6fc has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-bc8c250ccd has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.