_Filed by the scheduled full-suite report, not written by a person. It holds no pull, batch or release._
2 files failed in the full suite on main (check run 01m7grnpp4tfjfad83wsn4krb9, ed44b87), filed as one issue: one run red for one cause starts one builder.
test/release-handover.test.ts
test/landsim.test.ts
test/release-handover.test.ts
a push in flight on the old forge completes across the roll, and no connection is refused
a push in flight on the old forge completes across the roll, and no connection is refused failed: error: expect(received).toBeGreaterThan(expected)
2026-11-15T23:30:24.108Z INFO [forge] sharing the data directory with a live forge socket=forge-01m7grrach7fbarj9t27vb2ctt.sock
22 | test("a push in flight on the old forge completes across the roll, and no connection is refused", () => {
23 | expect(across.status).toBe(200);
24 | expect(across.report).toContain("unpack ok");
25 | expect(across.report).toContain("ok refs/heads/main");
26 | expect(across.tookMs).toBeGreaterThanOrEqual(PUSH_MS * 0.9);
27 | expect(across.asked).toBeGreaterThan(100);
^
error: expect(received).toBeGreaterThan(expected)
Expected: > 100
Received: 79
at <anonymous> (test/release-handover.test.ts:27:24)
(fail) a push in flight on the old forge completes across the roll, and no connection is refused [0.48ms]
To reproduce:
bun test ./test/release-handover.test.ts
bun test ./test/release-handover.test.ts --rerun-each10
The full suite ran it in shard 19/3535, 4 files at a time.
test/landsim.test.ts
the whole file took 28.8 s, over the 20 s file budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
the landing simulator > seed 3 lands what was reviewed, apart from the violations an issue owns took 2.76 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
the landing simulator > seed 5: pulls that only add lines merge, landed 2 then 1 took 2.04 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
a push in flight on the old forge completes across the roll, and no connection is refused
a push in flight on the old forge completes across the roll, and no connection is refused failed
2 of 3535 shards failed:
(fail) a push in flight on the old forge completes across the roll, and no connection is refused [0.48ms] [shard 19]
To reproduce:
bun test ./test/landsim.test.ts
bun test ./test/landsim.test.ts --rerun-each10
The full suite ran it in shard 322/3535, 4 files at a time.
_Filed by the scheduled full-suite report, not written by a person. It holds no pull, batch or release._
2 files failed in the full suite on main (check run 01m7grnpp4tfjfad83wsn4krb9, ed44b87), filed as one issue: one run red for one cause starts one builder.
test/release-handover.test.tstest/landsim.test.tstest/release-handover.test.tsa push in flight on the old forge completes across the roll, and no connection is refuseda push in flight on the old forge completes across the roll, and no connection is refusedfailed:error: expect(received).toBeGreaterThan(expected)To reproduce:
The full suite ran it in shard 19/3535, 4 files at a time.
test/landsim.test.tsthe whole file took 28.8 s, over the 20 s file budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issuethe landing simulator > seed 3 lands what was reviewed, apart from the violations an issue owns took 2.76 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issuethe landing simulator > seed 5: pulls that only add lines merge, landed 2 then 1 took 2.04 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issuea push in flight on the old forge completes across the roll, and no connection is refuseda push in flight on the old forge completes across the roll, and no connection is refusedfailedTo reproduce:
The full suite ran it in shard 322/3535, 4 files at a time.
Files: test/release-handover.test.ts, test/landsim.test.ts