-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[3/N] Add -Wdeprecated and related fixes #109698
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/109698
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 f44426e with merge base 428cbd7 ( UNSTABLE - The following job failed but was likely due to flakiness present on trunk and has been marked as unstable:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
9b389d9
to
01224f5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor changes / questions
not looking at this until the first two PRs successfully land and stick |
A strange IOS failure, no clue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, after reading the other comments I agree with @ezyang, let's wait a bit to make sure the other PRs stuck then merge this in.
@cyyever are you on slack? I think we may need some messaging for the other two PRs |
Unrelated failures. |
@pytorchbot rebase |
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
Successfully rebased |
2af1afe
to
5310dde
Compare
@pytorchbot rebase |
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
Successfully rebased |
5310dde
to
3e70b01
Compare
@pytorchbot rebase |
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
Successfully rebased |
3e70b01
to
f44426e
Compare
@pytorchmergebot merge |
Merge startedYour 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 |
❌ 🤖 pytorchbot command failed:
Try |
1 similar comment
❌ 🤖 pytorchbot command failed:
Try |
@pytorchbot revert -m "breaking quantization tests ( quantization/test_quantize_per_channel_sub_byte and quantization/test_quantize_per_channel_float_qparams) internally" -c ghfirst It's unclear if the tests are also run externally/ why we don't see a similar breakage here. Regardless, here are the logs, hopefully they are helpful. test_quantize_per_channel_sub_byte
test_quantize_per_channel_float_qparams
|
@pytorchbot successfully started a revert job. Check the current status here. |
@cyyever your PR has been successfully reverted. |
This reverts commit c31fcda. Reverted #109698 on behalf of https://github.com/PaliC due to breaking quantization tests ( quantization/test_quantize_per_channel_sub_byte and quantization/test_quantize_per_channel_float_qparams) internally ([comment](#109698 (comment)))
This PR follows #108626. Hopefully we can enable the warning in the next PR.
cc @EikanWang @jgong5 @voznesenskym @penguinwu @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @Xia-Weiwen @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler @ezyang @Skylion007