Conversation
|
cc: @fadara01 |
|
@pytorchbot merge |
|
PR targets viable/strict rather than main, refusing merge request |
|
@pytorchbot rebase |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
0f1c359 to
1c58f07
Compare
|
@pytorchbot rebase main |
|
❌ 🤖 pytorchbot command failed: Try |
|
@pytorchbot rebase -h |
PyTorchBot HelpMergeRevertRebaseLabelDr CIcherry-pick |
|
@pytorchbot rebase -r main |
|
❌ 🤖 pytorchbot command failed: Try |
|
@pytorchbot merge -r main |
|
PR targets viable/strict rather than main, refusing merge request |
|
@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 "Let's test in prod" |
|
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 |
This PR needs a
|
Fixes compiler warnings thrown by Clang-21
Fixes #166755
cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10 @jerryzh168 @aditew01 @snadampal @milpuz01 @nikhil-arm @fadara01 @H-Huang @awgu @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @pragupta @msaroufim @dcci @voznesenskym @penguinwu @EikanWang @Guobing-Chen @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @chenyang78 @kadeng @muchulee8 @amjames @chauhang @aakhundov @coconutruben @Lucaskabela