CI time limit on the step; no timeout in Dockerfile or scripts (closes #199)
check / check (push) Canceled after 0s
check / check (push) Canceled after 0s
The runner ignores a job's timeout-minutes, so the 20-minute limit moves to the step that runs script/cibuild. The Dockerfile frontend-test stage, script/frontend-test and script/frontend-viewport-test drop their timeout wrappers, which failed make check on a busy host. go test's -timeout 90s stays, as REPO_POLICIES.md requires it. Model: opus-5-5
This commit is contained in:
1 parent
437e0ea80c
commit
62f593f49a
5 files changed
+15
-9
No files matched your search
@@ -23,6 +23,11 @@ Run `make frontend-viewport-test` in CI as its own step; it is not part of
|
||||
|
||||
# Completed Steps
|
||||
|
||||
- 2026-11-10: the CI time limit of 20 minutes is on the step that runs
|
||||
`script/cibuild` ([#199](https://git.eeqj.de/sneak/netwatch/issues/199)). The
|
||||
runner ignored it on the job. The `Dockerfile`, `script/frontend-test` and
|
||||
`script/frontend-viewport-test` no longer wrap commands in `timeout`, so
|
||||
`make check` has no time limit outside CI.
|
||||
- 2026-10-26: `README.md`, `TODO.md` and `test/viewport/README.md` are rewritten
|
||||
sentence by sentence ([#189](https://git.eeqj.de/sneak/netwatch/issues/189)).
|
||||
Each sentence reads on the first pass: one idea, under about 30 words, the
|
||||
|
||||
Reference in new issue
Block a user