Flaky: test/security-merge.test.ts #2104

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

• merge correctness (clean results, recorded for regression) > a conflicting merge attempt leaves the base ref completely unchanged
• merge correctness (clean results, recorded for regression) > refs/pull/N/merged survives git gc --prune=now
• merge correctness (clean results, recorded for regression) > squash merge produces exactly one parent; regular merge produces exactly two

First failure:

error: expect(received).toBe(expected)

Expected: "commit"
Received: ""

Red seeds: 2974524939, 2783989559, 976843847, 1461733334, 1292515689. Reproduce: bun test --randomize --seed=2974524939 ./test/security-merge.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/security-merge.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.