[DevX] Add tool and doc on partial debug builds#116521
Conversation
Turned command sequence mentioned in https://dev-discuss.pytorch.org/t/how-to-get-a-fast-debug-build/1597 and in varios discussions into a tool that I use almost daily to debug crashes or correctness issues in the codebase
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/116521
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (1 Unrelated Failure)As of commit bfe0163 with merge base 87da0e1 ( FLAKY - The following job failed but was likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
atalman
left a comment
There was a problem hiding this comment.
LGTM, but lint needs to be fixed
|
@pytorchbot merge -f "lint is green" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
|
I'm curious what you think is the UX tradeoff between a separate script vs using an env variable + the usual setup.py develop ? |
Turned command sequence mentioned in https://dev-discuss.pytorch.org/t/how-to-get-a-fast-debug-build/1597 and in various discussions into a tool that I use almost daily to debug crashes or correctness issues in the codebase
Essentially it allows one to turn this:
into this
while retaining good performance for the rest of the codebase