Open mcepl opened 1 month ago
It's definitely possible that this is a Cython issue (I think we'd like to test some non-x64 architectures but it proved hard to do).
But it definitely isn't obvious that it is from what you posted. It'd think it's just as likely to be in HDF5 or an error in their code that calls it.
I don't want to dismiss it out-of-hand but I don't think we're the people to start investigating this.
On Mon Oct 14, 2024 at 10:27 PM CEST, da-woods wrote:
It's definitely possible that this is a Cython issue (I think we'd like to test some non-x64 architectures but it proved hard to do).
But it definitely isn't obvious that it is from what you posted. It'd think it's just as likely to be in HDF5 or an error in their code that calls it.
Possible, I just hoped that you would know better how much you care about armv7l and/or where to ask for more questions better than this overloaded Python package maintainer.
how much you care about armv7l
In principle it should work and we'd want to fix any bugs stopping it from working. However it's poorly tested on our side.
where to ask for more questions better than this overloaded Python package maintainer.
My uninformed guess is that it's an alignment error (i.e. it's trying to use data that isn't aligned like arm wants it to be). The first thing I'd do to debug it would be to build it with C debug symbols and try to catch it in gdb.
My thought is that the h5py maintainers would be best to make the first pass at that - they probably understand their build system and tests
Describe the bug
While packaging python-h5py for openSUSE, the running of test suite fails completely on armv7l:
Complete build log with all packages used and log of all steps taken to reproduce.
Everything works correctly on other platforms.
Code to reproduce the behaviour:
see above, just run the test suite
Expected behaviour
test suite passes on all platforms
OS
Linux (openSUSE/Tumbleweed)
Python version
3.10.15 (but probably obsereveable on others)
Cython version
3.0.11
Additional context
No response