review-runs-tracking: 2026-11 #1492

Activity

1. dormouse-bot

   added

   review-runs-trackingMonthly tracking issue for review-runs below-threshold findingsMonthly tracking issue for review-runs below-threshold findings

   on Nov 1, 2026
2. dormouse-bot commented on Nov 1, 2026

   

   dormouse-bot

   on Nov 1, 2026

   CollaboratorAuthor

   More actions

   Run 41316592241 — 2026-11-01T14:40:41Z

   Window 2026-10-31T13:54:05Z → run start (~24.5 h). 88 tend runs censused (not a page boundary): tend-mention 46 (39 success, 7 skipped), tend-review 14, tend-mention-relay 11, tend-ci-failures 10, tend-notifications 5, nightly 1, review-runs 1. Zero failures. The longest run was nightly 41311085957 at 22 min against the default 360-min cap, so nothing ran long or near the timeout. Token report: $20.04 over 22 priced sessions: tend-review 14 / $8.32, nightly $7.20, notifications 3 / $2.07, review-runs $1.31, mention 3 / $1.14. No outliers: the costliest review was $0.98 (#1475).

   Argos flagged 3 NetworkSettings screenshots on every PR because the stories read the real clock. Acted on: #1493

   • Evidence level: High (deterministic, reproduced)
   • Occurrences this run: 4 Argos builds (2071–2074, on bot PRs Restart a Copy button's feedback timer on a repeat click #1490 and Correct test comments that claim more than their tests check #1491)
   • Run ID: 41316592241
   • Workflow: https://github.com/diffplug/dormouse/actions/runs/41316592241
   • Detail: Nightly 41311085957 attributed the matching 3-screenshot diff on its comment- and test-only PRs to "drift" without finding a cause. Argos's public GraphQL (app.argos-ci.com/graphql, no auth) names the screenshots as modals-networksettings--{anywhere-enrolled,local-networks-enrolled,self-host}. Comparing the base and compared images of build 2073 shows one difference: "Paired Oct 31" against "Paired today". The stub's pairedDevices stamps the phone at Date.now() - 1h, and main's baseline (builds 2063/2064 for ef7a2be) rendered at 00:19 UTC, so every PR built after 01:00 differs. This is the same class of bug Pin the access-log story's timestamps to the story clock #1487 fixed for RemoteControlSection. Pin the NetworkSettings stories to a fixed clock so Argos stops flagging "Paired today" #1493 pins the NetworkSettings meta clock. Moving STORY_NOW to 00:10 temporarily reproduces "Paired Jan 14", which shows the pin now controls that line. All 20 stories pass in chromium. On Pin the NetworkSettings stories to a fixed clock so Argos stops flagging "Paired today" #1493 everything is green except Argos, which flags exactly the three predicted screenshots (builds 2075/2076) and waits for a maintainer to accept them. Next sweep: if Pin the NetworkSettings stories to a fixed clock so Argos stops flagging "Paired today" #1493 has merged, rerun Argos on Restart a Copy button's feedback timer on a repeat click #1490 and Correct test comments that claim more than their tests check #1491. Refuse a .. step behind a backslash in a browser binary path #1479 and Correct stale comments left by alert deferral's removal and dor remote routing #1480 need main merged in, because their diff, remotecontrolsection--paired-phones-and-access-log, predates Pin the access-log story's timestamps to the story clock #1487 on their branches. Deferred until Pin the NetworkSettings stories to a fixed clock so Argos stops flagging "Paired today" #1493 lands, so the merge does not just swap one stale diff for another.
   • Lesson for sessions: when Argos is red on a PR whose diff cannot reach a story, query the build's screenshotDiffs on the public GraphQL endpoint and compare the images instead of writing it off as drift.

   Sessions sampled: sound

   • Nightly 41311085957 ($7.20): it opened chore: update tend workflows (0.3.22 → 0.3.23) #1488 (tend 0.3.23), Test the pgstencil provenance gate before a Hosted production deploy #1489 (a verifyPackages test, mutation-checked), Restart a Copy button's feedback timer on a repeat click #1490 (CopyButton timer, with a test that fails first) and Correct test comments that claim more than their tests check #1491 (test-comment accuracy). It refreshed tend check: configuration drift on diffplug/dormouse #1069. The work was sound, apart from the Argos attribution above.
   • Notifications 41235405949: it saw that Pin the access-log story's timestamps to the story clock #1487 had re-baselined main, reran Argos on Log a one-time connection's end when it was replaced or disposed #1483 as a control, then on Abandon a Surface move whose late iframe consent would replace a newer question #1482 and fix: say an unsaved VS Code revocation lasts until the broker window closes #1485, and all three went green. That was good recovery without a push. Notifications 41262629717 correctly acknowledged 8 threads that were already handled, without posting.

   Maintainer corrections

   review-runs-corrections ran: 5 dispositions (#1478, #1481, #1482, #1483 and #1485, all bot PRs, merged), 16 comment rows and 0 review rows. The nedtwigg rows (#1473 ×3) apply bot findings. The rest are Cloudflare deploy comments and the audit status. No maintainer corrections.

   Live scan

   • Issues: none needs a worker. Security audit status #1137 turned PASS→FAIL at 11:30Z with one embargoed ledger finding (disclosure 11-08), which is maintainer-owned. VS Code: a revocation whose save failed lasts until the broker window closes, not until Dormouse quits #1484 stays open by design. [workflow-audit] 1 unexplained change(s) on 2026-10-31 #1486 was answered last sweep. Track Tauri GTK upgrade to remediate glib advisory #663 is maintainer-owned.
   • PRs: chore: update tend workflows (0.3.22 → 0.3.23) #1488 and Test the pgstencil provenance gate before a Hosted production deploy #1489 are green and await a maintainer (restricted). Refuse a .. step behind a backslash in a browser binary path #1479, Correct stale comments left by alert deferral's removal and dor remote routing #1480, Restart a Copy button's feedback timer on a repeat click #1490 and Correct test comments that claim more than their tests check #1491 are red only on Argos (see above). Drafts Design account-wide devices: the Relay keeps no device list #1473–Raise a prompt on a stray key in command mode instead of passing it #1476 have reviews at their live heads.
   • Default branch: red-default-branch-runs reached back to 2026-10-16T19:23:21Z with no candidates.
   • Waiting runs: only hosted-preview.yml, which is maintainer-gated. Dependabot: glib maybe: drop node-pty for a Rust backend #1 only, tracked by Track Tauri GTK upgrade to remediate glib advisory #663. Outage trackers: none.

   Pre-registered watches

   • tend-notifications under-delivery, occurrence 51: 5 runs in ~24 h against */15. No lever.
   • chore: update tend workflows (0.3.19 → 0.3.22) #1478 security-rule amendment: resolved. The maintainer merged it at 00:12Z, accepting the S41/S61 loosening for setup-runtime. Retire the watch.
   • Nightly/review double-post on nightly's red PRs: not repeated.