_Filed by the scheduled full-suite report, not written by a person. It holds no pull, batch or release._
3 files failed in the full suite on main (check run 01m7gawk2nkg0670wwre9nzdy4, 065f7a1), filed as one issue: one run red for one cause starts one builder.
test/tui-backups.test.ts
test/feature-clock-schedule.test.ts
test/protection.test.ts
test/tui-backups.test.ts
the snapshot destination in the terminal > no frame ever held the access key or the secret key took 2.16 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
To reproduce:
bun test ./test/tui-backups.test.ts
bun test ./test/tui-backups.test.ts --rerun-each10
The full suite ran it in shard 612/3476, 4 files at a time.
test/feature-clock-schedule.test.ts
the clock > across the spring change (2026-03-08) too, and a daily at fires once on that 23-hour day took 2.64 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
To reproduce:
bun test ./test/feature-clock-schedule.test.ts
bun test ./test/feature-clock-schedule.test.ts --rerun-each10
The full suite ran it in shard 633/3476, 4 files at a time.
test/protection.test.ts
AppsRuntime.start and startCrew each note what they lack took 4.21 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
the snapshot destination in the terminal > no frame ever held the access key or the secret key took 2.16 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
the clock > across the spring change (2026-03-08) too, and a daily at fires once on that 23-hour day took 2.64 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issue
To reproduce:
bun test ./test/protection.test.ts
bun test ./test/protection.test.ts --rerun-each10
The full suite ran it in shard 2989/3476, 4 files at a time.
_Filed by the scheduled full-suite report, not written by a person. It holds no pull, batch or release._
3 files failed in the full suite on main (check run 01m7gawk2nkg0670wwre9nzdy4, 065f7a1), filed as one issue: one run red for one cause starts one builder.
test/tui-backups.test.tstest/feature-clock-schedule.test.tstest/protection.test.tstest/tui-backups.test.tsthe snapshot destination in the terminal > no frame ever held the access key or the secret key took 2.16 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issueTo reproduce:
The full suite ran it in shard 612/3476, 4 files at a time.
test/feature-clock-schedule.test.tsthe clock > across the spring change (2026-03-08) too, and a daily at fires once on that 23-hour day took 2.64 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issueTo reproduce:
The full suite ran it in shard 633/3476, 4 files at a time.
test/protection.test.tsAppsRuntime.start and startCrew each note what they lack took 4.21 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issuethe snapshot destination in the terminal > no frame ever held the access key or the secret key took 2.16 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issuethe clock > across the spring change (2026-03-08) too, and a daily at fires once on that 23-hour day took 2.64 s, over the 2 s test budget: make it faster, or name its file in SLOW in scripts/gate.ts with an issueTo reproduce:
The full suite ran it in shard 2989/3476, 4 files at a time.
Files: test/tui-backups.test.ts, test/feature-clock-schedule.test.ts, test/protection.test.ts