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

Flaky: test/policy.test.ts #2109

shipped production is serving it opened this has it
opened this

test/policy.test.ts is red in 9 of 10 runs of bun scripts/flake-hunt.ts admit test/policy.test.ts (random order, under load), so #261 could not admit it to the gate. It stays in EXCLUDED in scripts/gate.ts under this issue.

The seeds reproduce exactly without load, so this is an order dependency inside the file: a test relies on state that an earlier test leaves behind, or a later test breaks state that an earlier one set up. It is not a timing race.

Tests seen failing:

  • a pull at the wall > the crew never lands a green pull across the wall; a person still can
  • a pull at the wall > the pull page says so, in the same sentences

First failure:

error: "unknown_head"
      at <anonymous> (/data/crew/mason/01m23vygyffx5hg2f5vm8r74sr/261/test/policy.test.ts:275:32)
(fail) a pull at the wall > the crew never lands a green pull across the wall; a person still can [16.84ms]

Red seeds: 2638743751, 3763444762, 653512626, 97567816, 2201069976, 3483924780, 3583720022, 1641799002, 4292298042. Reproduce: bun test --randomize --seed=2638743751 ./test/policy.test.ts.

Done looks like

  • [ ] Each test in the file sets up what it reads, so the file is green in any order. Do not add retries, and do not weaken an assertion.
  • [ ] bun scripts/flake-hunt.ts admit test/policy.test.ts is 10/10 green, and its record is in the pull.
  • [ ] The file's row moves from EXCLUDED to GATE in scripts/gate.ts in the same pull.
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs