pytest-dev / pytest-dev/pytest

pdb + expect tests failing in Python 3.7

Open
#10,042 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

platform: linux plugin: debugging type: infrastructure
Dominant language
Python
Stars
14.5k
Forks
3.4k
Avg merge
2d 9h
Merged PRs (30d)
35

Description

Link to a failing build:

https://github.com/pytest-dev/pytest/runs/6860982658

FAILED testing/test_debugging.py::TestPDB::test_pdb_interaction_capturing_simple - pexpect.exceptions.TIMEOUT: Timeout exceeded.
FAILED testing/test_debugging.py::TestPDB::test_pdb_interaction_capturing_twice - pexpect.exceptions.TIMEOUT: Timeout exceeded.
FAILED testing/test_debugging.py::TestPDB::test_pdb_with_injected_do_debug - assert False
FAILED testing/test_debugging.py::TestDebuggingBreakpoints::test_pdb_not_altered - pexpect.exceptions.TIMEOUT: Timeout exceeded.
FAILED testing/test_debugging.py::test_pdb_suspends_fixture_capturing[capfd] - assert 'out_inner' not in ') c\r\n\r\n...========\r\n'
FAILED testing/test_debugging.py::test_pdb_suspends_fixture_capturing[capsys] - assert 'out_inner' not in ') c\r\n\r\n...========\r\n'

Marking those tests as xfail so they get out of the way for now, but the cause of the errors should be investigated eventually.

Tests marked as xfail in #10043.

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 with the failing build and the listed tests in testing/test_debugging.py, running them under Python 3.7. Review the xfail changes referenced in #10043 and investigate the pdb/expect interaction behind the timeouts and assertions. Done means the affected tests pass without the temporary xfails.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.