KEMBAR78
[FSDP][Wrap] ModuleWrapPolicy callable by rohan-varma · Pull Request #109117 · pytorch/pytorch · GitHub
Skip to content

Conversation

@rohan-varma
Copy link
Contributor

@rohan-varma rohan-varma commented Sep 12, 2023

Stack from ghstack (oldest at bottom):

Makes ModuleWrapPolicy callable, in my case this is needed for
composition with or_policy. We should also make or_policy a public interface
IMO.

Differential Revision: D49175112

Makes ModuleWrapPolicy callable, in my case this is needed for
composition with or_policy. We should also make or_policy a public interface
IMO.

Differential Revision: [D49175112](https://our.internmc.facebook.com/intern/diff/D49175112/)

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Sep 12, 2023

🔗 Helpful Links

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

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

❌ 1 New Failure, 1 Unrelated Failure

As of commit 42c32f4 with merge base b2cba43 (image):

NEW FAILURE - The following job has failed:

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

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

rohan-varma added a commit that referenced this pull request Sep 12, 2023
Makes ModuleWrapPolicy callable, in my case this is needed for
composition with or_policy. We should also make or_policy a public interface
IMO.

Differential Revision: [D49175112](https://our.internmc.facebook.com/intern/diff/D49175112/)

ghstack-source-id: 200376033
Pull Request resolved: #109117
Makes ModuleWrapPolicy callable, in my case this is needed for
composition with or_policy. We should also make or_policy a public interface
IMO.

Differential Revision: [D49175112](https://our.internmc.facebook.com/intern/diff/D49175112/)

[ghstack-poisoned]
Copy link
Contributor

@fegin fegin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rohan-varma
Copy link
Contributor Author

@awgu is it OK for ModuleWrapPolicy?

@awgu
Copy link
Collaborator

awgu commented Sep 13, 2023

I think this is okay. I wonder if we should add a unit test though.

Makes ModuleWrapPolicy callable, in my case this is needed for
composition with or_policy. We should also make or_policy a public interface
IMO.

Differential Revision: [D49175112](https://our.internmc.facebook.com/intern/diff/D49175112/)

[ghstack-poisoned]
rohan-varma added a commit that referenced this pull request Sep 14, 2023
Pull Request resolved: #109117

Makes ModuleWrapPolicy callable, in my case this is needed for
composition with or_policy. We should also make or_policy a public interface
IMO.
ghstack-source-id: 200666498
@exported-using-ghexport

Differential Revision: [D49175112](https://our.internmc.facebook.com/intern/diff/D49175112/)
@rohan-varma
Copy link
Contributor Author

That can be a good ramp up task: #109266

@rohan-varma
Copy link
Contributor Author

dynamo tests are unrelated

@rohan-varma
Copy link
Contributor Author

@pytorchbot merge -f "CI done"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants