From 6b4a294db0a3aa89a1dc0ac4f8543f07dd4fad0d Mon Sep 17 00:00:00 2001 From: emi Date: Tue, 21 Jul 2026 16:22:34 -0700 Subject: [PATCH] Fix CI boot check take 4: 30s timeout too short under CI load Confirmed via a real run's own docker logs: the container actually booted successfully (migrations + 4 uvicorn workers, "Application startup complete") but took just over 30s under this runner's resource contention (capacity 2 -- another job's build often runs concurrently), where the same boot takes ~3s locally with nothing else competing for CPU. Give it 60s instead. --- .forgejo/workflows/build.yml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/.forgejo/workflows/build.yml b/.forgejo/workflows/build.yml index 6f05351..41664fa 100644 --- a/.forgejo/workflows/build.yml +++ b/.forgejo/workflows/build.yml @@ -49,8 +49,13 @@ jobs: docker run -d --name "$name" \ -e THERMOGRAPH_FRONTEND_BASE_INTERNAL=http://127.0.0.1:1 \ -p "127.0.0.1:${port}:8137" thermograph-backend:ci + # 60s, not 30 -- confirmed by a real run's own docker logs: alembic + # migrations + starting 4 uvicorn workers took just over 30s under + # this runner's resource contention (capacity 2, so another job's + # build often runs concurrently), even though the same boot takes + # ~3s locally with nothing else competing for CPU. ok=0 - for i in $(seq 1 30); do + for i in $(seq 1 60); do if curl -fsS -o /dev/null "http://127.0.0.1:${port}/healthz"; then ok=1; break; fi sleep 1 done