Segmentation fault in JIT tests on Windows CPU
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17.9k
- Forks
- 7.3k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 13
Description
For example: https://github.com/pytorch/vision/actions/runs/5519380703/jobs/10067038151#step:9:964
Looking at the HUD, I'm seeing the first occurrence of this around June 28 nightlies.
However, the job is flaky and passes from time to time. Chance of passing is different for the same job on different Python versions. Not sure if that actually plays a role, but it underlines the flakiness.
- A passing job from the same run as above but with a different Python version: https://github.com/pytorch/vision/actions/runs/5519380703/jobs/10067040388
- Different run than above, but same job passing there: https://github.com/pytorch/vision/actions/runs/5499611221/jobs/10021935529
cc @seemethere
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 with the failing Windows CPU JIT job linked in the issue, then compare it with the passing jobs from the same and another run. Use the HUD link to inspect the first occurrences around the June 28 nightlies and compare Python versions. Done means identifying and fixing the segmentation fault so the affected tests pass reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100