-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[3/N] Fix cppcoreguidelines-special-member-functions warnings #138796
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/138796
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 5bf59f3 with merge base d2ec289 ( 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. |
|
@pytorchbot label "topic: not user facing" |
|
need rebase |
|
@pytorchbot 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 merge -f "CI passed before" |
|
The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
|
@pytorchmergebot revert -m "reverting since this started failing a windows test" |
|
❌ 🤖 pytorchbot command failed: Try |
|
@pytorchmergebot revert -m "reverting since this started failing a windows test" -c ignoredsignal |
|
@pytorchbot successfully started a revert job. Check the current status here. |
|
Don't want to revert based on edited command |
|
@pytorchmergebot revert -m "reverting since this started failing a windows test" -c ignoredsignal |
|
@pytorchbot successfully started a revert job. Check the current status here. |
|
@cyyever your PR has been successfully reverted. |
#138796)" This reverts commit 7cb3cef. Reverted #138796 on behalf of https://github.com/wdvr due to reverting since this started failing a windows test ([comment](#138796 (comment)))
|
@pytorchbot 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 merge -i |
|
The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command |
Merge startedYour change will be merged while ignoring the following 1 checks: trunk / macos-py3-arm64 / test (default, 1, 3, macos-m1-stable) Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Follows #138796 Pull Request resolved: #139027 Approved by: https://github.com/ezyang
Fixes #ISSUE_NUMBER