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

Flaky: test/search.test.ts #2105

shipped production is serving it opened this has it
opened this

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

  • search: one query, four sources > local repo hits carry their open counts

First failure:

error: expect(received).toMatchObject(expected)

  {
-   "openIssues": 2,

Red seeds: 3987236623, 2510124947, 3910044882, 1075785985, 3572094342. Reproduce: bun test --randomize --seed=3987236623 ./test/search.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/search.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