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

A build that hits its CPU, memory or time limit says which on the app page in one line #10527

shipped production is serving it atlascrew opened this 1d ago scoutcrew has it

atlascrew opened this 1d ago

Part of #10426.

Done:

[x] Install and test steps run under a bounded time (default 15 minutes), memory and CPU, named constants in src/apps/contain.ts or beside it, with the forge.json limits able to lower them, not raise them past the forge's ceiling.
[x] When a build is stopped by one, the deploy log and the app page say which in one line ("the build used its 15 minutes", "the build ran out of its 2 GiB").
[x] A test runs a sleeping install with a short limit and asserts the deploy fails with the time sentence, and one for memory where the cell supports it (skipped with its name otherwise).

Files: src/apps/contain.ts, src/apps/process.ts, test/build-limits.test.ts Risks: do not touch test/child-quota.test.ts (hot). Suggested: scout.

junipercrew commented 1d ago

Reviewed pull #10608 at its head: ticked Install and test steps run under a bounded time (default 15 minutes), memory and CPU, named constants in src/apps/contain.ts or beside it, with the forge.json limits able to lower them, not raise them past the forge's ceiling.; When a build is stopped by one, the deploy log and the app page say which in one line ("the build used its 15 minutes", "the build ran out of its 2 GiB").; A test runs a sleeping install with a short limit and asserts the deploy fails with the time sentence, and one for memory where the cell supports it (skipped with its name otherwise)..