Description of problem: It looks like pymapvbvd assumes that both the binary file format and the host running the code are little-endian. Version-Release number of selected component (if applicable): 0.5.4-2.fc39 How reproducible: Steps to Reproduce: 1. Remove “ExcludeArch: s390x” 2. fedpkg scratch-build --srpm --arches s390x Actual results: =========================== short test summary info ============================ FAILED tests/test_flags.py::test_flagRemoveOS - IndexError: index -1 is out o... FAILED tests/test_flags.py::test_flagIgnoreSeg_flagDoAverage - IndexError: in... FAILED tests/test_flags.py::test_flagSkipToFirstLine - IndexError: index -1 i... FAILED tests/test_read.py::test_gre - IndexError: index -1 is out of bounds f... FAILED tests/test_read.py::test_epi - IndexError: index -1 is out of bounds f... FAILED tests/test_slicing.py::test_vb - IndexError: index -1 is out of bounds... FAILED tests/test_svs.py::test_vb - IndexError: index -1 is out of bounds for... FAILED tests/test_svs.py::test_ve - IndexError: index -1 is out of bounds for... FAILED tests/test_svs.py::test_vb_broken - IndexError: index -1 is out of bou... ======================== 9 failed, 17 warnings in 1.31s ======================== Expected results: All tests pass, as they do on other platforms. Additional info: If the file format is always little-endian, this should mostly be a matter of making endianness explicit when creating a numpy array that is to be copied bytewise in or out of the file: for example, np.dtype('<u4') instead of np.uint32. However, there are a lot of places this would need to be done, and it would require some time and study for me to offer a careful patch—probably more time than I want to spend on it. Upstream would be open to fixing this, but can’t dedicate the time currently if there aren’t a substantial number of potential users on s390x. https://github.com/wtclarke/pymapvbvd/issues/35
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '39'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 39 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26. Fedora Linux 39 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.