tmux-python / tmux-python/libtmux

Tests failing on ppc64le

Open
#477 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I am packaging libtmux for openSUSE. Unfortunately the tests fail on ppc64le. Could you have a look if this can be fixed?

[   82s] =================================== FAILURES ===================================
[   82s] ___________________ test_function_times_out_no_raise_assert ____________________
[   82s] 
[   82s]     def test_function_times_out_no_raise_assert() -> None:
[   82s]         ini = time()
[   82s]     
[   82s]         def never_true() -> bool:
[   82s]             return False
[   82s]     
[   82s]         assert not retry_until(never_true, 1, raises=False)
[   82s]     
[   82s]         end = time()
[   82s]     
[   82s] >       assert abs((end - ini) - 1.0) < 0.01
[   82s] E       assert 0.012233734130859375 < 0.01
[   82s] E        +  where 0.012233734130859375 = abs(((1679485925.7025032 - 1679485924.6902695) - 1.0))
[   82s] 
[   82s] tests/test_test.py:67: AssertionError
[   82s] _______________________ test_function_times_out_no_rise ________________________
[   82s] 
[   82s]     def test_function_times_out_no_rise() -> None:
[   82s]         ini = time()
[   82s]     
[   82s]         def never_true() -> bool:
[   82s]             return False
[   82s]     
[   82s]         retry_until(never_true, 1, raises=False)
[   82s]     
[   82s]         end = time()
[   82s]     
[   82s] >       assert abs((end - ini) - 1.0) < 0.01
[   82s] E       assert 0.013442516326904297 < 0.01
[   82s] E        +  where 0.013442516326904297 = abs(((1679485936.5801134 - 1679485935.566671) - 1.0))
[   82s] 
[   82s] tests/legacy_api/test_test.py:54: AssertionError

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

Start by running the failing tests in tests/test_test.py and tests/legacy_api/test_test.py on ppc64le, focusing on the retry_until timeout assertions shown in the report. Check how the timing tolerance behaves on that platform; done means the tests pass there while still verifying the intended one-second timeout behavior.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.