Conversation
Adds two new workflows: - weekly-pytorch-pin-bump.yml: Weekly cron that bumps the PyTorch nightly pin, syncs c10 headers, and creates a PR - pin-bump-ci-handler.yml: Watches trunk CI on pin bump PRs and posts @claude comments to fix failures (up to 3 attempts), then escalates to a human Authored with Claude.
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/19034
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (2 Unrelated Failures)As of commit e650c7f with merge base 9600f63 ( BROKEN TRUNK - The following jobs failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
meta-cla
Bot
added
the
CLA Signed
This PR needs a
|
|
|
||
| This PR was created automatically. If CI fails, Claude will attempt to fix issues (up to 3 attempts). If CI still fails, human review will be requested. | ||
|
|
||
| cc @jakeszwe |
There was a problem hiding this comment.
Ideally this should be oncall but ok for now
There was a problem hiding this comment.
Yeah I wasnt sure how to tag oncall in OSS
| `Failed run: ${runUrl}`, | ||
| '', | ||
| 'Please:', | ||
| '1. Read the Dr. CI comment on this PR for a summary of which jobs failed and whether they are flaky. Ignore failures marked as FLAKY.', |
There was a problem hiding this comment.
what if something which is not flaky but was broken on main before the pin bump for unrelated reasons, should we ask it to look at main? And try to see if they are failing similarly after the bump?
There was a problem hiding this comment.
Gonna see if its smart enough to recognize stuff that was broken before. Will iterate on the prompt if not.
2 participants
Adds two new workflows:
Authored with Claude.