pytest-dev / pytest-dev/pytest-rerunfailures
timeout error not handled in CI run
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 477
- Forks
- 107
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 21
Description
This failure was not handled correctly: https://github.com/pyinstaller/pyinstaller/runs/2309970398
arguments were as follows:
C:\hostedtoolcache\windows\Python\3.8.8\x64\Scripts\pytest.exe -n 3 --maxfail 3 --durations 10 tests/unit tests/functional --force-flaky --no-flaky-report --reruns 3 --reruns-delay 10 -o timeout_func_only=true
============================= test session starts =============================
platform win32 -- Python 3.8.8, pytest-6.2.3, py-1.10.0, pluggy-0.13.1 -- c:\hostedtoolcache\windows\python\3.8.8\x64\python.exe
cachedir: .pytest_cache
rootdir: D:\a\pyinstaller\pyinstaller, configfile: setup.cfg
plugins: flaky-3.7.0, drop-dup-tests-0.3.0, forked-1.3.0, rerunfailures-9.1.1, timeout-1.4.2, xdist-2.2.1
timeout: 300.0s
timeout method: thread
timeout func_only: True
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.
Research direction
Start with the linked CI run and reproduce the shown pytest command, including --reruns, --reruns-delay, and -o timeout_func_only=true. Trace how a timeout is handled alongside reruns and define completion as the timeout being processed correctly in this CI scenario.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100