Tests failing on ppc64le
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- testing-qa
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.
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
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 127
- Avg merge
- 2h 13m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tmux-python/libtmux
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
tmux-python/libtmux#759 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tmux-python/libtmux#745 · 2 comments ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tmux-python/libtmux#744 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tmux-python/libtmux#731 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tmux-python/libtmux#654 ·
All issues in tmux-python/libtmux
Similar issues
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100