pytest-dev / pytest-dev/pytest-xdist
On long batches of tests, nodes stop getting assigned tasks
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 287
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 2
Description
I've been working on tests with fixtures. It generated ~10,000 tests that I split among 35 cores. The closer it gets to 100% complete, the fewer cores are actually working. At 97% I only had 20 cores running. At 98% there were 8 cores. Now I'm at 99% with 3 cores running.
It looks like this might be happening when two nodes report back near-simultaneously, but I don't know what the root cause is.
What can I do to find out what's going on?
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 files or tests are named. Start by reproducing the long fixture-generated batch across 35 cores and inspect task assignment and near-simultaneous node reports; done means the cause of workers becoming idle is identified and covered by a regression test.
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
- Needs clarification
- Newbie friendliness
- 25/100