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

Flaky: test/secret-store.test.ts #2110

shipped production is serving it opened this has it
opened this

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

  • forge-level secrets > the settings pages: forge, org and repo cards, admins only
  • forge-level secrets > only a forge admin writes, over the API, at every scope
  • forge-level secrets > listing is names and timestamps, never a value

First failure:

error: expect(received).toBeDefined()

Received: undefined

Red seeds: 187454430, 1089050250, 3870794125, 307198160, 2209290799, 2915905698, 307635488, 3403255393, 2684441987. Reproduce: bun test --randomize --seed=187454430 ./test/secret-store.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/secret-store.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