Public: anyone can read this; the crew can change it.

Revert "The attention budget covers every top-level page, and a page without a row fails the test" #13174

Merged opened this

Check · Review · Land · Live done — Landed and live in production.

Merged

Reverts #13024: verifying main after landing found it broke "copying the database does not hold the serving thread (#7559) took 2.16 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue" and 2 more in test/deadends.test.ts, test/attention.test.ts, test/backup-truth.test…

Notes

shipped production is serving it deploy 59903fa

opened this

Reverts #13024: verifying main after landing found it broke "copying the database does not hold the serving thread (#7559) took 2.16 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue" and 2 more in test/deadends.test.ts, test/attention.test.ts, test/backup-truth.test.ts — found by bisecting d357679..6b4bd0f in 4 steps.

Main's verification 01m7f54qnnp2mmsy66n4yg6rhy is red at 6b4bd0f; each failed test fails alone too.

Proposed by the forge; a person lands it.

Files: test/deadends.test.ts, test/attention.test.ts, test/backup-truth.test.ts

Approved

A clean revert of #13024 that puts main back to green, which is the pipeline-first priority. The diff only removes the five added budget rows (apps, pricing, docs, security, people) and the five paths in test/attention.test.ts. It restores the earlier crew and repository numbers and the explore note position. No feature, no UI, no new code, so nothing here touches the security, terminal or README rules. Two things to do next: (1) re-land the attention-budget coverage for those five pages as a separate small pull once the slow-test cause is understood: the 2.16 s database copy test in backup-truth and the deadends test were tripped by it, so find what made them slow (likely the extra page fetches sharing the process) instead of re-adding the pages blindly. (2) Add a guard so a test-only or JSON-budget pull that makes an unrelated test exceed its time budget is caught in the pull's own gate, not only in main verification (#1242 / gate on impact).

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs