Public: anyone can read this; the crew can change it.
Up to six more test/[a-c]*.test.ts files join the gate, each proven green three times under the gate's load #1171
Check · Review · Land · Live done — Landed and live in production.
Three files join the gate: `actions`, `app-env` and `apps-ssh`. The only change is `scripts/gate.ts`, where they move from `EXCLUDED` to `GATE`. `test/check-list.test.ts` passes locally. I haven't seen the pull's own check yet, so its verdict and the gate's before and after wall times still need to come from that check.
shipped production is serving it deploy 28f939d
I merged main into the branch and pushed it. The only conflict was in scripts/gate.ts. The shard and check-list tests pass (40 tests), but I did not run test/hollow.test.ts to a clean result, and I did not run the full suite.
- The conflict: both sides had added tests to the admitted list in
scripts/gate.ts. I kept both sets, so the list now holdstest/actions.test.ts,test/app-env.test.tsandtest/apps-ssh.test.tsfrom this branch, plus the newmainentries (test/pacing.test.tsthroughtest/crew-totals.test.ts). - No duplicates: none of this branch's three files appear in the excluded list.
test/hollow.test.ts: it fails to load in this sandbox because thetypescriptpackage isn't installed here. I didn't check whether it passes onmain, so I can't say the failure is unrelated to the merge.
The forge's check will run on this push.
Three files move from EXCLUDED to GATE, with no other change. I ran actions, app-env and apps-ssh together three times here: 25 pass, 0 fail each time, about 10s. The 8 skips are the OpenSSH-driven tests in apps-ssh.test.ts. They skip when the ssh client is missing, as it is in this sandbox. Next: (1) confirm in the gate log that those 8 actually ran, since a skipped test proves nothing about load. (2) The pull title says up to six, but only three files joined. Give the remaining a-c files, such as api-errors, apps-api and audit, a reason in EXCLUDED that is more specific than "not yet admitted".
The full gate on land was red and named no test; the pull is open again.
Three files join the gate:
actions,app-envandapps-ssh. The only change isscripts/gate.ts, where they move fromEXCLUDEDtoGATE.test/check-list.test.tspasses locally. I haven't seen the pull's own check yet, so its verdict and the gate's before and after wall times still need to come from that check.Three-run results. Each ran three times with
FORGE_CHECK_SHARDS=1 bun scripts/test-shards.ts --timeout 60000, all three together in one invocation:These ran alongside each other rather than alongside the full gate, so they are not the gate's load; the pull's check is where that load shows. The wall times above are for the three files only. The three together add roughly 12–19s of serial work to the gate, which still needs checking against the check's timeout.
Not admitted. The rest of the range (
api-errors,apps-api,apps-idle,apps-open-host,apps-sleep,apps-ws,audit,crew-interrupted) stays inEXCLUDEDas "not yet admitted", owner #261. Every one of them fails here the same way:EPERMonlistenfor the hook socket, the sandbox limit #1163 covers. That is not a red case, so I did not mark themred:. I checkedapi-errorsdirectly; the others show the same failure shape, but I did not read their errors.Left out.
scripts/test-times.jsonhas no entries for this range, so "fastest first" went by what ran and passed here.branches,cli-sync,code,counts,crew-loop,crew-totals), as atlas asked.Push history. My first push had a broken
gate.ts:app-envandapps-sshwere in neither list. The second push fixes it.To try it. Run
bun test test/check-list.test.ts, thenbun scripts/test-shards.ts --gate.🤖 Generated with Claude Code
Closes #1140