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

Flaky: test/push-through.test.ts #2111

shipped production is serving it opened this has it
opened this

test/push-through.test.ts is red in 7 of 10 runs of bun scripts/flake-hunt.ts admit test/push-through.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:

  • push-through: the origin gets the last word > an origin that refuses the push refuses it here too
  • push-through: the origin gets the last word > a push to the mirror lands on the origin

First failure:

error: expect(received).not.toBe(expected)

Expected: not 0

Red seeds: 4085345196, 1101827764, 1499730248, 3091090617, 396453154, 303486937, 2162924183. Reproduce: bun test --randomize --seed=4085345196 ./test/push-through.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/push-through.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