KEMBAR78
[torchx] Do not terminate parent process if exit code from child isn't valid by atuljangra · Pull Request #111961 · pytorch/pytorch · GitHub
Skip to content

Conversation

@atuljangra
Copy link
Contributor

Summary:
There's no reason to terminate the parent process trying to find the name of the signal received by the child process.
Let's make sure this is handled properly, which then will ensure that parent process can process child failures.

Test Plan: Unit tests.

Reviewed By: aaronenyeshi

Differential Revision: D50615419

@pytorch-bot
Copy link

pytorch-bot bot commented Oct 24, 2023

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/111961

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 64a9f4a with merge base ad4971c (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Oct 24, 2023

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: atuljangra / name: Atul Jangra (64a9f4a)

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D50615419

@atuljangra
Copy link
Contributor Author

Added the correct email address as well.

@aaronenyeshi
Copy link
Member

/easycla

@aaronenyeshi
Copy link
Member

Added the correct email address as well.

That check is passing now, once all the signals pass, we can use pytorchbot to merge this PR.

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D50615419

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D50615419

…t valid (pytorch#111961)

Summary:

There's no reason to terminate the parent process trying to find the name of the signal received by the child process.
Let's make sure this is handled properly, which then will ensure that parent process can process child failures.

Test Plan: Unit tests.

Reviewed By: aaronenyeshi

Differential Revision: D50615419
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D50615419

@facebook-github-bot
Copy link
Contributor

@pytorchbot merge

(Initiating merge automatically since Phabricator Diff has merged)

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Oct 25, 2023
@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

xuhancn pushed a commit to xuhancn/pytorch that referenced this pull request Nov 7, 2023
…t valid (pytorch#111961)

Summary:
There's no reason to terminate the parent process trying to find the name of the signal received by the child process.
Let's make sure this is handled properly, which then will ensure that parent process can process child failures.

Test Plan: Unit tests.

Reviewed By: aaronenyeshi

Differential Revision: D50615419

Pull Request resolved: pytorch#111961
Approved by: https://github.com/aaronenyeshi
Skylion007 pushed a commit to Skylion007/pytorch that referenced this pull request Nov 14, 2023
…t valid (pytorch#111961)

Summary:
There's no reason to terminate the parent process trying to find the name of the signal received by the child process.
Let's make sure this is handled properly, which then will ensure that parent process can process child failures.

Test Plan: Unit tests.

Reviewed By: aaronenyeshi

Differential Revision: D50615419

Pull Request resolved: pytorch#111961
Approved by: https://github.com/aaronenyeshi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk Trigger trunk jobs on your pull request fb-exported Merged topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants