indygreg / indygreg/python-zstandard

Test failure on 32-bit Intel-compatible architecture

Open
#147 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
642
Forks
116
Avg merge
1d 14h
Merged PRs (30d)
5

Description

While building on the 32-bit Intel compatible architecture ('i386'), we see this test failure:

```
======================================================================
FAIL: test_estimated_compression_context_size (tests.test_data_structures.TestCompressionParameters)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/tmp/guix-build-python-zstandard-0.15.2.drv-0/zstandard-0.15.2/tests/test_data_structures.py", line 104, in test_estimated_compression_context_size
self.assertAlmostEqual(
AssertionError: 1294656 != 1295064 within 400 delta (408 difference)

----------------------------------------------------------------------
Ran 278 tests in 0.866s

FAILED (failures=1, skipped=42)
Test failed:
error: Test failed:
command "python" "-c" "import setuptools, tokenize;__file__='setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\\r\\n', '\\n');f.close();exec(compile(code, __file__, 'exec'))" "test" failed with status 1

```

I noticed that Gentoo is skipping the test: https://bugs.gentoo.org/773979

Can you advise if this test should be skipped? Or does it highlight a real problem with python-zstandard on the 32-bit Intel architecture?

Contributor guide

Open the contributing guide

Research direction

Start with tests/test_data_structures.py and test_estimated_compression_context_size, then run the failing test on a 32-bit Intel-compatible build. Compare the reported size difference with the test's expected value and determine whether the implementation or architecture-specific assertion is wrong; done means deciding between a fix and an explicitly justified skip.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
operating-systems, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.