Run only script/cibuild in the Gitea workflow (closes #203) #322

Merged
clawbot merged 1 commits from issue-203-ci-cibuild-only into next 2026-10-21 13:23:00 +02:00
3 changed files with 8 additions and 4 deletions
-1
View File
@@ -18,4 +18,3 @@ jobs:
# All history and tags, so git describe finds the version tag.
fetch-depth: 0
- run: script/cibuild
- run: script/docker-smoke
+5
View File
@@ -30,6 +30,11 @@ P2: security: per-origin rate limiting
# Completed Steps
- 2026-10-21 the Gitea workflow checks out the repo and runs `script/cibuild`,
nothing else (closes #203): its `script/docker-smoke` step is removed, as the
canonical `REPO_POLICIES.md` says, since `make check` covers what CI needs to
check. CI no longer starts the image and waits for its healthcheck.
`script/docker-smoke` and `make docker-smoke` stay, to run by hand.
- 2026-10-20 a WebP, AVIF or JPEG XL encode at the limits takes at most about 34
seconds (closes #272): with one libvips thread, 8192x8192 random pixels with
an alpha channel took about 61 seconds to encode as WebP, 81 as JPEG XL and,
+3 -3
View File
@@ -1,8 +1,8 @@
#!/bin/sh
# script/docker-smoke: build the Docker image, start it, and wait up to
# 30 seconds for its HEALTHCHECK to report healthy. Needs a Docker
# daemon, so it is not part of script/check; the Gitea workflow runs it
# after script/cibuild.
# 30 seconds for its HEALTHCHECK to report healthy. It is not part of
# script/check, which never starts the image, and the Gitea workflow
# does not run it. Run it by hand.
set -eu
SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd -P)"