tmux-python / tmux-python/libtmux

Intermittent errors with tests on i586 (32bit)

Open
#481 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.2k
Forks
127
Avg merge
2h 13m
Merged PRs (30d)
1

Description

When packaging this for openSUSE Tumbleweed, we get intermittent build errors due to failing tests.

Today this one errored out (using tmux-3.3a) on i586 (32bit):

[   81s] =================================== FAILURES ===================================
[   81s] ___________________ test_function_times_out_no_raise_assert ____________________
[   81s] 
[   81s]     def test_function_times_out_no_raise_assert() -> None:
[   81s]         ini = time()
[   81s]     
[   81s]         def never_true() -> bool:
[   81s]             return False
[   81s]     
[   81s]         assert not retry_until(never_true, 1, raises=False)
[   81s]     
[   81s]         end = time()
[   81s]     
[   81s] >       assert abs((end - ini) - 1.0) < 0.01
[   81s] E       assert 0.011504411697387695 < 0.01
[   81s] E        +  where 0.011504411697387695 = abs(((1679550658.3015473 - 1679550657.2900429) - 1.0))
[   81s] 
[   81s] tests/legacy_api/test_test.py:67: AssertionError
[   81s] =============================== warnings summary ===============================
[...]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The failure is in tests/legacy_api/test_test.py, specifically test_function_times_out_no_raise_assert; start by reading that test and the retry_until call it exercises. Reproduce or inspect the timing behavior on 32-bit i586, then make the test reliably validate the timeout and run the affected test.

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
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.