Skip to content

review-runs-tracking: 2026-11 #94

Open

Description

@selfie-bot

Monthly tracking issue for observations and diagnoses. Each run appends findings as a comment. Future runs read these to build cumulative evidence.

Do not close manually — a new issue is created each month, and prior months are closed automatically.

Activity

  1. selfie-bot commented on Nov 20, 2026

    @selfie-bot
    CollaboratorAuthor

    Run 44772909954 — 2026-11-20T16:27:18Z

    This is the repo's first review-runs sweep, so there was no earlier tracker and the window starts at the floor of 2026-11-19T15:25:04Z. The review-runs-tracking label did not exist, so prepare-evidence failed until this run created it.

    Census: 37 completed runs: 35 successful, 1 failed, and 1 skipped. No jobs ran long or near their timeout, and no runs are wedged in waiting. The 12 runs with a model session cost $6.16 in total: review $2.68 over 7 runs, triage $1.44 over 2, nightly $1.30 over 1, and notifications $0.74 over 2. There were no outliers. Maintainer corrections: none. The script returned three comment rows, but all were on threads nedtwigg owns (#79 and #26) and none contradicted the bot.

    Outcomes checked: the bot approved #85, #88 and #89, and #85 and #88 merged. #87 was the bot's triage PR. Its change was duplicated by the maintainer's #88, and the bot closed #87 as superseded. #92 (a survey fix) and #93 (workflow regeneration) are open with green CI. Triage of #86 found that the cause was the deploy token's missing R2 permission. That diagnosis held: #88 recorded that the token was updated and the rerun succeeded.

    tend-review on #89 lost to a Claude binary install failure

    • Evidence level: Low (single occurrence, transient)
    • Occurrences this run: 1
    • Run ID: 44691789758
    • Workflow: https://github.com/diffplug/selfie/actions/runs/44691789758
    • Session: none, because the run failed before the agent started
    • Detail: install-claude-binary.sh (tend 0.3.27) failed with "✘ Couldn't install Claude Code". The next review run, 3 minutes later on the same version, installed fine. The script makes one attempt, and tend main has no retry either. Upstream already declined retry wrappers for these installs: #906 was closed unmerged and #909 was closed as not planned. So nothing was filed. Recovery worked: notifications run 44706961617 approved The hackathon's bucket is deleted, so step 5 no longer mentions it #89 at head f59c341. Outage tracker Bot temporarily unavailable #90 is drained by this sweep.

    Nightly summary misattributed the #89 approval

    Run 44920205842 — 2026-11-21T15:40:06Z

    Census: 11 completed runs since 2026-11-20T16:23:31Z, all successful: tend-mention ×3, tend-notifications ×4, tend-nightly, tend-review (#93), tend-triage (#94), and tend-review-runs. No jobs ran long or near their timeout, nothing is wedged in waiting, and there were no outage trackers. The 7 runs that took about 15 seconds (mention and notifications) skipped before the model started, so they have no session log and are designed no-ops. Cost: $2.76 over the 4 sessions: nightly $1.19, review-runs $1.01, review $0.41, triage $0.15. There were no outliers. Maintainer corrections: none. The script ran and returned empty dispositions, comments, and reviews.

    Sessions reviewed: 44773254951 (triage on #94) correctly left the bot's tracker without a comment. 44915207671 (review on #93) checked the 0.3.28 bump and the deletion of tend-install-test.yaml. It verified that no ruleset requires install-test and that CI was green. It posted nothing, as it should for the bot's own PR under restricted mode. 44914870828 (nightly) passed the PAT and tend check audits, found no conflicts, surveyed 13 files without finding a PR's worth, and pushed the 0.3.28 regeneration to #93 as 0d5e1f3, which went green.

    Follow-up on the earlier finding "Nightly summary misattributed the #89 approval": this nightly described the failed #89 review run and the later approval accurately. It did not repeat the mistake.

    No new findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    review-runs-trackingMonthly tend review-runs evidence tracker

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions