Commit 4ae7641
test(knowledge): give the member-tombstone budget test its own timeout
`finishes a pass within its page budget` times out against the shared 30s
default on a loaded CI runner. It is a load flake, not a regression: the same
commit went green on the `push` integration job and timed out on `migrate`,
and it runs in ~4s locally.
The cost is real work, not a hang. The test seeds
`MEMBER_TOMBSTONE_RECONCILE_PAGES_PER_RUN * 500 + 500` documents specifically
so one pass cannot finish inside a single run's budget, then observes and
re-lists all of it. That volume is the assertion, so trimming it to fit the
default would stop proving the multi-run path. Given its own 120s budget
instead, matching the per-test timeouts already used elsewhere in this
directory, with a comment recording why.
Unrelated to this branch's fork-sync work - the file is byte-identical to
staging and arrived with the merge - but it was failing this PR's CI, and a
flake left alone becomes one everybody learns to ignore.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>1 parent f79b234 commit 4ae7641
1 file changed
Lines changed: 10 additions & 1 deletion
Lines changed: 10 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
360 | 360 | | |
361 | 361 | | |
362 | 362 | | |
| 363 | + | |
| 364 | + | |
| 365 | + | |
| 366 | + | |
| 367 | + | |
| 368 | + | |
| 369 | + | |
| 370 | + | |
| 371 | + | |
363 | 372 | | |
364 | 373 | | |
365 | 374 | | |
| |||
404 | 413 | | |
405 | 414 | | |
406 | 415 | | |
407 | | - | |
| 416 | + | |
408 | 417 | | |
409 | 418 | | |
410 | 419 | | |
| |||
0 commit comments