chadtmiller.com/knotless
git that lives in your Atmosphere account
1
10
The prod runner's runs get 7 GiB each
.knotless/workflows/deploy.yml+4−3
| @@ -51,9 +51,10 @@ env: | ||
# (--pulls-only there, deploy/runner-host), off this one's CPU, but a | ||
# queued pull's pre-flights and each batch run here. Uncapped, one test | ||
# takes about 9 GiB and every core, and two stalled the host: two jobs | ||
# of 3 CPUs and 6 GiB leave serve 2 cores and some 4 GB, and a run past | ||
# its memory fails its step rather than the host. | ||
KNOTLESS_RUN_ARGS: --queue --jobs 2 --cpus 3 --memory 6 | ||
# of 3 CPUs and 7 GiB leave serve 2 cores and some 2 GB, with swap the | ||
# margin, and a run past its memory fails its step rather than the host. | ||
# At 6 GiB, compiling knotless-serve for coverage was killed. | ||
KNOTLESS_RUN_ARGS: --queue --jobs 2 --cpus 3 --memory 7 | ||
# The runner host's account (deploy/runner-host), which a new public | ||
# repository names unless its owner names others: it runs anyone's. | ||
KNOTLESS_DEFAULT_RUNNER_DID: did:plc:4bocpkn5zkwe4wuu4plrj5kt | ||
deploy/README.md+1−1
| @@ -418,7 +418,7 @@ watch only repositories whose writers you trust. The step containers have | ||
no limits of their own beyond `--step-timeout` unless `KNOTLESS_RUN_ARGS` | ||
gives them (`--cpus`, `--memory`, `--pids`, `--network`, `--run-timeout`: | ||
see [the CLI reference](../docs/reference/cli.md)). knotless's own deploy | ||
gives them in `deploy.yml`: two jobs of 3 CPUs and 6 GiB, as one | ||
gives them in `deploy.yml`: two jobs of 3 CPUs and 7 GiB, as one | ||
coverage `test` uncapped takes about 9 GiB and every core, and two at | ||
once stalled the host. | ||