pytorch - ✅(Solved) Fix Bot to notify PoC if ci pin updater fails [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
pytorch/pytorch#177896Fetched 2026-04-08 01:03:03
View on GitHub
Comments
0
Participants
1
Timeline
24
Reactions
0
Author
Participants
Timeline (top)
subscribed ×14labeled ×5mentioned ×4added_to_project_v2 ×1

PR fix notes

PR #176956: [torchtitan hash update] update the pinned torchtitan hash

Description (problem / solution / changelog)

This PR is auto-generated nightly by this action. Update the pinned torchtitan hash.

Changed files

  • .github/ci_commit_pins/torchtitan.txt (modified, +1/-1)
RAW_BUFFERClick to expand / collapse

When the autoupdate bot fails to merge its nightly pin-update PR, the PR just keeps getting bumped night after night but nobody is notified. It would be nice to have a mechanism for listing owners for a particular CI pin, and then have them get cc'd with @ on the PR after first failure.

(note: it would be less desirable to be cc'd on the opening of the PRs, as this would be noisy on all the successful nights)

Example: https://github.com/pytorch/pytorch/pull/176956

Is there perhaps an existing bot or workflow that this could piggyback onto?

cc @seemethere @malfet @pytorch/pytorch-dev-infra @ZainRizvi @huydhn

extent analysis

Fix Plan

The fix involves implementing a notification mechanism for CI pin owners when the autoupdate bot fails to merge its nightly pin-update PR.

Steps

  • Create a new GitHub Actions workflow that runs on PR update events
  • Use the github.actions context to check if the PR is a pin-update PR and if it has failed to merge
  • Define a list of owners for each CI pin in a separate file (e.g. ci-pin-owners.yml)
  • Use the github.actions context to comment on the PR and CC the owners using @ mentions

Example Code

name: Notify CI Pin Owners

on:
  pull_request:
    types: [updated]

jobs:
  notify:
    runs-on: ubuntu-latest
    steps:
      - name: Check if PR is pin-update PR
        run: |
          if [ "$GITHUB_EVENT_NAME" == "pull_request" ] && [ "$GITHUB_EVENT_ACTION" == "updated" ]; then
            # Check if PR is pin-update PR
            if grep -q "pin-update" "$GITHUB_EVENT_PATH"; then
              # Check if PR has failed to merge
              if [ "$GITHUB_EVENT_PULL_REQUEST_STATE" == "open" ] && [ "$GITHUB_EVENT_PULL_REQUEST_MERGEABLE" == "false" ]; then
                # Get CI pin owners from file
                owners=$(yq e '.ci_pins["'"$GITHUB_EVENT_PULL_REQUEST_TITLE"'"].owners' ci-pin-owners.yml)
                # Comment on PR and CC owners
                github.actions/comment -b "CC @${owners//,/ @}"
              fi
            fi
          fi
# ci-pin-owners.yml
ci_pins:
  pytorch:
    owners: seemethere, malfet, pytorch/pytorch-dev-infra, ZainRizvi, huydhn

Verification

To verify that the fix worked, create a test PR that triggers the workflow and check if the owners are CC'd on the PR after the first failure.

Extra Tips

  • Make sure to update the ci-pin-owners.yml file with the correct owners for each CI pin.
  • You can customize the notification message by modifying the github.actions/comment step.
  • Consider adding a threshold for the number of failures before notifying the owners to avoid noise.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

pytorch - ✅(Solved) Fix Bot to notify PoC if ci pin updater fails [1 pull requests, 1 participants]