pytest-dev / pytest-dev/pytest-xdist
pytest-xdist doesn't recover from kernel killing a worker
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 287
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 2
Description
When run in an environment guarded by cgroups resource control (any cloud instance), sometimes the kernel kills one of the pytest workers if the total usage of RSS is bigger than the allowed quota. And while xdist notices that and starts a new worker, the test suite never recovers. All previously existing workers stop their work and are idling and nothing happens.
xdist definitely recovers from a test crashing a worker, but it doesn't seem to be the case with when a kernel does the killing.
The main issue here, is that the whole setup hangs, so on CIs it's a big problem.
Thank you!
Contributor guide
No contributing guide indexed for this repository
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
No file or test is named in the issue. Start by reproducing the hang under a cgroup RSS limit and compare it with recovery after a test crashes a worker; done means the suite continues after the kernel kills a worker, with regression coverage for that recovery path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100