Skip to content

Conversation

wz337
Copy link
Contributor

@wz337 wz337 commented Mar 5, 2024

[ghstack-poisoned]
@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Mar 5, 2024
wz337 added a commit that referenced this pull request Mar 5, 2024
ghstack-source-id: 76ade4f
Pull Request resolved: #121204
Copy link

pytorch-bot bot commented Mar 5, 2024

🔗 Helpful Links

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

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

✅ You can merge normally! (5 Unrelated Failures)

As of commit 8c0777f with merge base d7a5e59 (image):

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

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

@github-actions github-actions bot added oncall: distributed Add this issue/PR to distributed oncall triage queue module: distributed_checkpoint labels Mar 5, 2024
@wz337 wz337 changed the title remove unused variables [nit][DCP][DSD] Remove Unused Variables in test_state_dict.py Mar 5, 2024
@wz337 wz337 requested a review from fegin March 5, 2024 06:28
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.

Why does this change cause FSDP compilation state_dict error? Is the error pre-existed?

@wz337
Copy link
Contributor Author

wz337 commented Mar 5, 2024

Why does this change cause FSDP compilation state_dict error? Is the error pre-existed?

Seems like so. I am having this error locally and I don't think it's related to the change, so I push just push these two-line changes definitely unrelated to double check.

….py"

cc mrshenli pritamdamania87 zhaojuanmao satgera rohan-varma gqchen aazzolini osalpekar jiayisuse H-Huang kwen2501 awgu penguinwu fegin XilunWu wanchaol fduwjj tianyu-l wconstab yf225 chauhang LucasLLC

[ghstack-poisoned]
wz337 added a commit that referenced this pull request Mar 5, 2024
ghstack-source-id: 9fa63ee
Pull Request resolved: #121204
@@ -106,9 +106,6 @@ def _test_save_load(
# Then finally we can call set_state_dict().
if not isinstance(dist_optim, list):
dist_optim = [dist_optim]
curr_dist_msd, curr_dist_osd = get_state_dict(
Copy link
Collaborator

Choose a reason for hiding this comment

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

Hmm, should have been caught by F841

….py"

cc mrshenli pritamdamania87 zhaojuanmao satgera rohan-varma gqchen aazzolini osalpekar jiayisuse H-Huang kwen2501 awgu penguinwu fegin XilunWu wanchaol fduwjj tianyu-l wconstab yf225 chauhang LucasLLC

[ghstack-poisoned]
wz337 added a commit that referenced this pull request Mar 7, 2024
ghstack-source-id: 9b53e05
Pull Request resolved: #121204
@wz337
Copy link
Contributor Author

wz337 commented Mar 7, 2024

@pytorchmergebot merge -i

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Mar 7, 2024
@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 1 checks: pull / linux-focal-cuda11.8-py3.10-gcc9 / test (distributed, 1, 3, linux.8xlarge.nvidia.gpu)

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

@huydhn
Copy link
Contributor

huydhn commented Mar 8, 2024

@pytorchbot revert -m 'Sorry for reverting your PR, but the failure looks legit' -c ignoredsignal

@pytorchmergebot
Copy link
Collaborator

@pytorchbot successfully started a revert job. Check the current status here.
Questions? Feedback? Please reach out to the PyTorch DevX Team

@pytorchmergebot
Copy link
Collaborator

@wz337 your PR has been successfully reverted.

pytorchmergebot added a commit that referenced this pull request Mar 8, 2024
…#121204)"

This reverts commit 4186c36.

Reverted #121204 on behalf of https://github.com/huydhn due to Sorry for reverting your PR, but the failure looks legit ([comment](#121204 (comment)))
@wz337
Copy link
Contributor Author

wz337 commented Mar 12, 2024

@pytorchmergebot rebase

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Collaborator

Rebase failed due to

Aborting rebase because rebasing the branch resulted in the same sha as the target branch.
This usually happens because the PR has already been merged.  Please rebase locally and push.

Raised by https://github.com/pytorch/pytorch/actions/runs/8255571895

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 Merged oncall: distributed Add this issue/PR to distributed oncall triage queue Reverted topic: not user facing topic category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants