Unit test failure of zarr v3.1.x on BE architectures

[avalentino]

Zarr version

v3.1.2

Numcodecs version

v0.16.2

Python Version

3.13

Operating System

GNU/Linux (Debian Sid) on s390x

Installation

debian packages

Description

After the merge of #2874 we have re-enabled the unit-testing on BE architectures for builds for the zarr package on Debian.
Currently we have in the archive zarr v3.1.2.
Unfortunately we still have a large number of unit tests that fail on our BE architecture: s390x.

Related tickets are: #2874, #3005, #869.

Steps to reproduce

python3.13 -m pytest --hypothesis-profile ci -k "not is_empty"

Additional output

The full build log is available at https://ci.debian.net/packages/z/zarr/testing/s390x/64102540/
The relevant part containing the python unittetst log is also attached to this ticket.

_build-error-zarr-3.1.2-on-s290x.txt

[d-v-b]

thanks for reporting this, i'll look into fixing these things. do you have any recommendations for how we could run tests on a BE platform as part of our CI?

[avalentino]

No, sorry.

When I have to do it locally I do something similar to https://til.simonwillison.net/docker/emulate-s390x-with-qemu.

From a quick search I understand that https://github.com/docker/setup-buildx-action?tab=readme-ov-file could be relevant, but I'm not sure and I have never tried it.