pytest-dev / pytest-dev/pytest-xdist
Running multiple cases through xdist gets stuck around 95% of the time
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 287
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 2
Description
Hi, Ask for help~
2024-01-16 17:58:26.653 [gw6] [ 85%] FAILED test/xxxxxx/case
2024-01-16 17:58:27.014 test/xxxxxx/case
2024-01-16 17:59:35.797 [gw5] [ 86%] PASSED test/xxxxxx/case
2024-01-16 17:59:36.126 test/xxxxxx/case
2024-01-16 18:00:28.257 [gw0] [ 88%] FAILED test/xxxxxx/case
2024-01-16 18:00:28.268 test/xxxxxx/case
2024-01-16 18:02:36.356 [gw1] [ 90%] FAILED test/xxxxxx/case
2024-01-16 18:02:45.082 [gw6] [ 91%] FAILED test/xxxxxx/case
2024-01-16 18:04:27.782 [gw0] [ 93%] PASSED test/xxxxxx/case
2024-01-16 18:04:27.795 test/xxxxxx/case
2024-01-16 18:08:26.971 [gw0] [ 95%] PASSED test/xxxxxx/case
2024-01-16 18:08:26.987 test/xxxxxx/case
2024-01-16 18:08:26.989 [gw0] [ 96%] SKIPPED test/xxxxxx/case
2024-01-16 18:08:26.991 test/xxxxxx/case
What information do I need to provide?
pytest-xdist==3.5.0
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
Start by reproducing the hang with pytest-xdist 3.5.0 and collect the test command, environment, worker configuration, and complete logs requested by the issue. Done means the failure is reproducible with enough information to identify its cause and a regression check confirms that multiple cases no longer stall near completion.
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
- 25/100