python3-lz4 segfaults when running tests on x86_64-musl

[ahesford]

System

• xuname:

  Void 5.10.27_1 x86_64-musl AuthenticAMD uptodate FFFF

• package: python3-lz4-3.1.3_1

Expected behavior

Running xbps-src check python3-lz4 in an x86_64-musl masterdir should succeed.

Actual behavior

As run:

........................................................................ [ 14%]
..../void-packages/common/build-style/python3-module.sh: line 26:  6982 Segmentation fault      python3 -m pytest ${make_check_args} ${make_check_target}

Adding make_check_args="-v":

tests/block/test_block_0.py::test_1[data7-mode29-store_size1-dictionary4-return_bytearray1] PASSED [ 15%]
tests/block/test_block_0.py::test_2[data0-mode0-store_size0-dictionary0] /void-packages/common/build-style/python3-module.sh: line 26: 12230 Segmentation fault      python3 -m pytest ${make_check_args} ${make_check_target}

Steps to reproduce the behavior

# On an x86_64-musl host:
./xbps-src binary-bootstrap
# On an x86_64 host:
./xbps-src binary-bootstrap x86_64-musl

sed -i '/^build_style/a make_check_args="-v"' srcpkgs/python3-lz4/template

./xbps-src check python3-lz4

@ericonr, if you're bored and looking for something to think about. Alpine is no help because their version of py3-lz4 is much older.

[ahesford]

Note: this segfault also affects xpra when trying to connect to a remote session with, e.g.,

xpra start ssh:remote-hostname --exit-with-children --start-child xterm

because xpra tries to use lz4 compression. I believe this can be worked around in xpra by disabling lz4 compression using the --compressors=lzo,zlib argument or the compressors configuration option.

[github-actions[bot]]

Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.