Intermittent errors with tests on x86_64 / amd64
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with tests/test_pane.py:113 and reproduce the failure in the openSUSE Tumbleweed x86_64 environment using tmux-3.3a-2.2. Compare the captured pane output around test_capture_pane_start and establish a reliable test result for the intermittent behavior.
Written by the indexing model from the issue text.
Description
When packaging this for openSUSE Tumbleweed, we get intermittent build errors due to failing tests.
Today this one errored out:
[ 126s] =================================== FAILURES ===================================
[ 126s] ___________________________ test_capture_pane_start ____________________________
[ 126s]
[ 126s] session = Session($1 libtmux_udfg_nz8)
[ 126s]
[ 126s] def test_capture_pane_start(session: Session) -> None:
[ 126s] env = shutil.which("env")
[ 126s] assert env is not None, "Cannot find usable `env` in PATH."
[ 126s]
[ 126s] session.new_window(
[ 126s] attach=True,
[ 126s] window_name="capture_pane_start",
[ 126s] window_shell=f"{env} PS1='$ ' sh",
[ 126s] )
[ 126s] pane = session.attached_window.attached_pane
[ 126s] assert pane is not None
[ 126s] pane_contents = "\n".join(pane.capture_pane())
[ 126s] assert pane_contents == "$"
[ 126s] pane.send_keys(r'printf "%s"', literal=True, suppress_history=False)
[ 126s] pane_contents = "\n".join(pane.capture_pane())
[ 126s] assert pane_contents == '$ printf "%s"\n$'
[ 126s] pane.send_keys("clear -x", literal=True, suppress_history=False)
[ 126s] pane_contents = "\n".join(pane.capture_pane())
[ 126s] > assert pane_contents == "$"
[ 126s] E assert '$ printf "%s"\n$ clear -x' == '$'
[ 126s] E - $
[ 126s] E + $ printf "%s"
[ 126s] E + $ clear -x
[ 126s]
[ 126s] tests/test_pane.py:113: AssertionError
[ 126s] =============================== warnings summary ===============================
[...]
tmux version was tmux-3.3a-2.2.
- 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
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/open-webui#30750 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
OpenwaterHealth/openmotion-bloodflow-app#604 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100