pytest-dev / pytest-dev/pytest-xdist
If a worker exits with a non-zero status code pytest-xdist doesn't report failure
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 287
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 2
Description
We have a mechanic in Polars to install a timeout in a second thread which when triggered exits the process as hanging. We need this because for some bugs the entire process can hang in a Rust function.
This thus calls exit(1) directly, without invoking Python exceptions or sys.exit or anything of the sort. We have no alternative to this, we are unable to return to Python.
I'd like it if pytest-xdist would check the exit code of workers, and if it exited with a non-zero exit code it is treated as a crash, restarting said worker or if no further restarts are allowed, failing that test.
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
The issue names no files or tests. Locate pytest-xdist's worker-exit handling and restart/failure tests, then verify that a worker exiting with a non-zero status is treated as a crash, restarted when allowed, and reported as a test failure when no restart remains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100