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

Flaky: test/subscriptions.test.ts #2113

shipped production is serving it opened this has it
opened this

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

  • the pages > nobody but an admin reaches the pool
  • the pages > an admin keeps a share of each window for people, and sees each window
  • the pages > an organization's page carries the table for every repository under it
  • a run on a granted account > holds a run without a call while every account on the grant rests
  • the pool > picks the nearest grant whole, an agent's before everyone's, and rotates
  • the pages > the crew page grants it to the repository, and a run there picks it

First failure:

error: expect(received).toHaveLength(expected)

Expected length: 1
Received length: 0

Red seeds: 1245422313, 823496026, 493121355, 3914605992, 875789095, 2269484034, 4088655362, 1652543253, 2832622420, 1596575526. Reproduce: bun test --randomize --seed=1245422313 ./test/subscriptions.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/subscriptions.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