Hello, On Mon, Feb 13, 2023 at 09:40:29AM +0000, Adrian Glaubitz wrote:

Hi!

I'm trying to introduce python-websockets as a dependency to SUSE:SLE-15-SP1:Update.

Unfortunately, the testsuite of the package fails on s390x with the following testsuite failure (see below). I have been trying to reproduce the issue with upstream code checked out from git on a Debian s390x porterbox but even with 9.1, I am unable to reproduce the failure with Python 3.9 (I cannot test anything earlier).

Does anyone have a suggestion on how to resolve this problem? I would be very grateful if anyone has any tips.

Thanks, Adrian

=========================================================================================

[ 70s] + echo python3 [ 70s] + PYTHONPATH=/home/abuild/rpmbuild/BUILDROOT/python-websockets-9.1-150000.3.5.5.s390x/usr/lib64/python3.6/site-packages [ 70s] + python3 -m unittest [ 75s] .......................F.................................................................................................................... ............................................................................................................................................ ............................................................................................................................................ ............................................................................................................................................ ............................................................................................................................................ ............................................................................................................................................ ................................................ [ 75s] ====================================================================== [ 75s] FAIL: test_remote_no_context_takeover (tests.extensions.test_permessage_deflate.PerMessageDeflateTests) [ 75s] ---------------------------------------------------------------------- [ 75s] Traceback (most recent call last): [ 75s] File "/home/abuild/rpmbuild/BUILD/websockets-9.1/tests/extensions/test_permessage_deflate.py", line 213, in test_remote_no_context_takeover [ 75s] self.assertIn("invalid distance too far back", str(exc.exception)) [ 75s] AssertionError: 'invalid distance too far back' not found in 'Error -3 while decompressing data: Operation-Ending-Supplemental Code is 0x40'

This is where the message expected by the test is described https://stackoverflow.com/questions/40652405/zlib-error-3-while-decompressin... https://bugs.python.org/issue27164 You get a different message from zlib which may be due to some acceleration kicking in and consequently zlib forwarding an accelerator hardware error rather than generating its own. The results should depend on python and zlib version, too. YMMV If the problem is only that the failure message is different (and not that the accelerator fails because it is fed bad data while software impl succeeds or something) you can just update match. Thanks Michal