From 2d85ee5a2557b4b4e3e4c328f1f855d444beab6f Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Mon, 12 Oct 2026 17:34:32 -0700 Subject: [PATCH] docs(gitea-runner): first real use of the nh3-docker runner (vastblue pytest 4m45s vs 14m17s, n=1 each) --- stacks/gitea-runner/README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/stacks/gitea-runner/README.md b/stacks/gitea-runner/README.md index 2181123..2bd3c36 100644 --- a/stacks/gitea-runner/README.md +++ b/stacks/gitea-runner/README.md @@ -58,6 +58,10 @@ Its config is `conf/config.nh3-docker.yaml`, tighter than ana-docker's because n - `network: ""` gives every job its own network instead of traefik-net. - The timeout stays at 30 m. +**First real use:** vastblue/platform's python job moved here at c02048c. Run 11042 passed in 5 m; pytest +(~1,234 tests) took 4m45s, against 14m17s on ana-docker in run 11033. That is one run each, at different times of +day, so read it as a ballpark. The Postgres service, apt and npm all worked without the socket. + A job that needs docker inside it (buildx and the like) cannot run here; keep those on `pfi-fleet`. ⚠ nh3-docker's vCPU has no AVX2 either, so CPU-bound torch tests are no faster here. This runner fixes the disk, not the CPU.