update all builds and tests and lints in all dockerfiles in managed repos to use maximum process nice level (lowest priority)
Dockerfiles here: Dockerfile.
Definition of done:
Every RUN step in these Dockerfiles that builds, tests or lints (compiling, make build/test/check/lint/fmt-check, golangci-lint, go test, yarn/npm build or test, and the like) runs under nice -n 19, e.g. RUN nice -n 19 make test.
Steps that only install packages, download dependencies or copy files are left as they are.
The app's runtime CMD/ENTRYPOINT is not niced: the service runs at normal priority.
nice exists in every stage that uses it (busybox and coreutils both have it); if a stage lacks it, the PR says how it was handled.
The image still builds and make check is green; nothing else changes.
Model: opus-5-5
sneak, 2026-09-29 in chat (verbatim):
> update all builds and tests and lints in all dockerfiles in managed repos to use maximum process nice level (lowest priority)
Dockerfiles here: `Dockerfile`.
Definition of done:
- Every `RUN` step in these Dockerfiles that builds, tests or lints (compiling, `make build`/`test`/`check`/`lint`/`fmt-check`, `golangci-lint`, `go test`, `yarn`/`npm` build or test, and the like) runs under `nice -n 19`, e.g. `RUN nice -n 19 make test`.
- Steps that only install packages, download dependencies or copy files are left as they are.
- The app's runtime `CMD`/`ENTRYPOINT` is not niced: the service runs at normal priority.
- `nice` exists in every stage that uses it (busybox and coreutils both have it); if a stage lacks it, the PR says how it was handled.
- The image still builds and `make check` is green; nothing else changes.
Model: opus-5-5
clawbot
self-assigned this 2026-09-29 13:02:20 +02:00
This one is done by the single dedicated worker for the whole rollout (tracking: sneak/project-management#15), in its turn. Repo-managers: do not dispatch a worker for it; when its PR arrives on next, gate it with an independent reviewer and squash-merge it as usual.
Model: opus-5-5
This one is done by the single dedicated worker for the whole rollout (tracking: https://git.eeqj.de/sneak/project-management/issues/15), in its turn. Repo-managers: do not dispatch a worker for it; when its PR arrives on `next`, gate it with an independent reviewer and squash-merge it as usual.
Model: opus-5-5
Stopped on sneak's word, 2026-09-29 in chat (verbatim):
stop the rollout.
Why: a nice value only orders processes within their own CPU group, and every container (and every RUN step of a build) is its own group, so nice -n 19 inside a Dockerfile does not lower a build's priority against other containers. Closed without changes.
Model: opus-5-5
Stopped on sneak's word, 2026-09-29 in chat (verbatim):
> stop the rollout.
Why: a nice value only orders processes within their own CPU group, and every container (and every `RUN` step of a build) is its own group, so `nice -n 19` inside a Dockerfile does not lower a build's priority against other containers. Closed without changes.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
sneak, 2026-09-29 in chat (verbatim):
Dockerfiles here:
Dockerfile.Definition of done:
RUNstep in these Dockerfiles that builds, tests or lints (compiling,make build/test/check/lint/fmt-check,golangci-lint,go test,yarn/npmbuild or test, and the like) runs undernice -n 19, e.g.RUN nice -n 19 make test.CMD/ENTRYPOINTis not niced: the service runs at normal priority.niceexists in every stage that uses it (busybox and coreutils both have it); if a stage lacks it, the PR says how it was handled.make checkis green; nothing else changes.Model: opus-5-5
This one is done by the single dedicated worker for the whole rollout (tracking: sneak/project-management#15), in its turn. Repo-managers: do not dispatch a worker for it; when its PR arrives on
next, gate it with an independent reviewer and squash-merge it as usual.Model: opus-5-5
Stopped on sneak's word, 2026-09-29 in chat (verbatim):
Why: a nice value only orders processes within their own CPU group, and every container (and every
RUNstep of a build) is its own group, sonice -n 19inside a Dockerfile does not lower a build's priority against other containers. Closed without changes.Model: opus-5-5