Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix lint failures coming from #126035 #126378

Closed
wants to merge 5 commits into from

Conversation

huydhn
Copy link
Contributor

@huydhn huydhn commented May 16, 2024

MYPY somehow shows lots of local failures for me. The issue is tracked in #126361. This is only to keep trunk sane. These two line were added by #126035 as an attempt to fix lint there, but didn't seem to help.

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

Copy link

pytorch-bot bot commented May 16, 2024

🔗 Helpful Links

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

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 6368112 with merge base cdcba4d (image):

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.

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label May 16, 2024
@huydhn huydhn marked this pull request as ready for review May 16, 2024 05:04
@huydhn huydhn requested a review from a team as a code owner May 16, 2024 05:04
@huydhn
Copy link
Contributor Author

huydhn commented May 16, 2024

@pytorchbot merge -f 'Already rebase to main, lint jobs are green, trying to see if this helps'

@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

@huydhn
Copy link
Contributor Author

huydhn commented May 16, 2024

@pytorchbot revert -m 'Trying to add yet another lint fix from https://hud.pytorch.org/pr/pytorch/pytorch/126357 and will reland this' -c weird

@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 added a commit that referenced this pull request May 16, 2024
This reverts commit 5fa1f4c.

Reverted #126378 on behalf of https://github.com/huydhn due to Trying to add yet another lint fix from https://hud.pytorch.org/pr/pytorch/pytorch/126357 and will reland this ([comment](#126378 (comment)))
@pytorchmergebot
Copy link
Collaborator

@huydhn your PR has been successfully reverted.

@pytorch-bot pytorch-bot bot added module: distributed_checkpoint oncall: distributed Add this issue/PR to distributed oncall triage queue labels May 16, 2024
@huydhn
Copy link
Contributor Author

huydhn commented May 16, 2024

@pytorchbot merge -f 'Another attempt'

@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

@r-barnes
Copy link
Contributor

@huydhn - Do you think we'll be able to keep #126035 landed?

ZelboK pushed a commit to ZelboK/pytorch that referenced this pull request May 19, 2024
MYPY somehow shows lots of local failures for me.  The issue is tracked in pytorch#126361.  This is only to keep trunk sane.  These two line were added by pytorch#126035 as an attempt to fix lint there, but didn't seem to help.
Pull Request resolved: pytorch#126378
Approved by: https://github.com/kit1980
ZelboK pushed a commit to ZelboK/pytorch that referenced this pull request May 19, 2024
This reverts commit 5fa1f4c.

Reverted pytorch#126378 on behalf of https://github.com/huydhn due to Trying to add yet another lint fix from https://hud.pytorch.org/pr/pytorch/pytorch/126357 and will reland this ([comment](pytorch#126378 (comment)))
ZelboK pushed a commit to ZelboK/pytorch that referenced this pull request May 19, 2024
MYPY somehow shows lots of local failures for me.  The issue is tracked in pytorch#126361.  This is only to keep trunk sane.  These two line were added by pytorch#126035 as an attempt to fix lint there, but didn't seem to help.

Pull Request resolved: pytorch#126378
Approved by: https://github.com/kit1980
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants