test.test_concurrent_futures.test_deadlock test_pyrepl failed on 1-core-VM
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Bug report
Bug description:
While working on reproducible builds for openSUSE (sponsored by the NLnet NGI0 fund), I found that our python313 package fails to build on 1-core-VMs from two failing tests.
Full build log: https://rb.zq1.de/other/python313/build-j1.log
2 re-run tests:
test.test_concurrent_futures.test_deadlock test_pyrepl
2 tests failed:
test.test_concurrent_futures.test_deadlock test_pyrepl
447 tests OK.
Total duration: 3 hour 35 sec
Total tests: run=42,874 (filtered) failures=7 skipped=1,745
Total test files: run=466/468 (filtered) failed=2 skipped=15 resource_denied=4 rerun=2
If those tests cannot pass in such an env, they should be skipped automatically.
CPython versions tested on:
3.13
Operating systems tested on:
Linux
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 by reviewing the linked build log and reproducing test.test_concurrent_futures.test_deadlock and test_pyrepl on a one-core Linux VM. Determine whether the failures are specific to single-core environments, then make the affected tests skip automatically there; done means the tests no longer fail in that environment while the broader test run remains valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100