🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

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

✅ No Failures

As of commit c4babfb with merge base 30d8b30 ():
💚 Looks good so far! There are no failures yet. 💚

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

Looks like there are still some remaining periodic 12.1 jobs

Looks like there are still some remaining periodic 12.1 jobs

Yes, there are periodic and inductor, I'll create separate PRs to move them (unless you've already did)
But I'm a bit curious, why wasn't the migration complete.
@atalman do you know?

@malfet I believe we need to update our CUDA update runbook: https://github.com/pytorch/builder/blob/main/CUDA_UPGRADE_GUIDE.MD
cc @tinglvv @weiwangmeta

@malfet I believe we need to update our CUDA update runbook: https://github.com/pytorch/builder/blob/main/CUDA_UPGRADE_GUIDE.MD cc @tinglvv @weiwangmeta

Prob best to update it with some future-proof instructions (e.g. "use cs.github.com with queries FOO and BAR to find all workflows where we need to update the CUDA version") in addition to the sample PRs, which will go stale over time

@malfet I believe we need to update our CUDA update runbook: https://github.com/pytorch/builder/blob/main/CUDA_UPGRADE_GUIDE.MD cc @tinglvv @weiwangmeta

IMO every time one is doing migration two things should happen:

• Issue to be opened to track the migration
• Issue is closed only when all jobs mentioning deprecated cuda version are removed

@malfet I believe we need to update our CUDA update runbook: pytorch/builder@main/CUDA_UPGRADE_GUIDE.MD cc @tinglvv @weiwangmeta

IMO every time one is doing migration two things should happen:

• Issue to be opened to track the migration
• Issue is closed only when all jobs mentioning deprecated cuda version are removed

Agree on this let us create an issue and follow thru rest of the migration there

@pytorchbot merge -f "Slow workflow is green"

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