[inductor] Fix finalization issues when using multiprocessing#87725
[inductor] Fix finalization issues when using multiprocessing#87725zdevito wants to merge 1 commit intogh/zdevito/199/basefrom
Conversation
If python was launched with 'spawn' it will not use the standard shutdown methods that concurrent.futures requires. So we register a shutdown with the method it does uses. Without this, shutdown hangs since the workers will not exit. [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/87725
Note: Links to docs will display an error until the docs builds have been completed. ❌ 3 Failures, 5 PendingAs of commit bbb1b2c: The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This PR needs a labelIf your changes are user facing and intended to be a part of release notes, please use a label starting with If not, please add the For more information, see https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work. |
|
@pytorchbot merge -f "CI failures appear unrelated" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
…h#87725) If python was launched with 'spawn' it will not use the standard shutdown methods that concurrent.futures requires. So we register a shutdown with the method it does uses. Without this, shutdown hangs since the workers will not exit. cc @jansel @mlazos @soumith @voznesenskym @yanboliang @penguinwu @anijain2305 Pull Request resolved: pytorch#87725 Approved by: https://github.com/wconstab
…h#87725) If python was launched with 'spawn' it will not use the standard shutdown methods that concurrent.futures requires. So we register a shutdown with the method it does uses. Without this, shutdown hangs since the workers will not exit. cc @jansel @mlazos @soumith @voznesenskym @yanboliang @penguinwu @anijain2305 Pull Request resolved: pytorch#87725 Approved by: https://github.com/wconstab
Stack from ghstack (oldest at bottom):
If python was launched with 'spawn' it will not use the standard
shutdown methods that concurrent.futures requires. So we register a
shutdown with the method it does uses. Without this, shutdown hangs
since the workers will not exit.
cc @jansel @mlazos @soumith @voznesenskym @yanboliang @penguinwu @anijain2305