From 34fd3936655de23328d2c2707fc2c9701302e688 Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 8 Nov 2026 16:35:01 -0600 Subject: [PATCH] docs(ci): describe the desktop CI runner, not gitdan-ci Comment and doc wording only, from the non-blocking findings on daniel/gitdan#114. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01MfBCVP2GbKqXSmmJXRPnXP --- .gitea/workflows/ci.yaml | 4 ++-- README.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.gitea/workflows/ci.yaml b/.gitea/workflows/ci.yaml index 4e36fb1..fb76c00 100644 --- a/.gitea/workflows/ci.yaml +++ b/.gitea/workflows/ci.yaml @@ -16,7 +16,7 @@ on: # cost and the evidence are in README's Development section. types: [opened, synchronize, reopened, edited] -# The desktop runner (gitdan#112) has few slots, and the compiler-backed +# The desktop runner (gitdan#112) has exactly one slot (the `desktop` label, capacity 1), and the compiler-backed # suites below are multi-minute. A superseded run costs a slot in front of # somebody's build, so drop it. # @@ -47,7 +47,7 @@ jobs: # `mktemp -d` and want a cold target dir every time — a persistent cache # would make "did this run rebuild?" unanswerable, which is the question # restore-mtimes-selftest.sh exists to ask. So this job takes no share of - # the shared CI cache disk budget. + # the host's shared CI cache disk budget (ci_cache_reclaim). steps: - name: Checkout sources uses: actions/checkout@v4 diff --git a/README.md b/README.md index 8330841..0e03d65 100644 --- a/README.md +++ b/README.md @@ -719,7 +719,7 @@ its bare default; either restores the bug. run.** Gitea populates no `changes` field for a title-or-body edit, unlike GitHub, so the workflow cannot tell the edit that un-drafts a PR from an ordinary body PATCH — a closing-reference fix-up, say. The price is around -**90 seconds** of a runner shared across four repos on two capacity slots: the +**90 seconds** of a runner shared across several repos (one capacity-1 `desktop` slot now; measured on gitdan-ci's two): the last twelve non-skipped runs of this job, `started_at` to `completed_at` off the Actions API, are 83 s median over 77–106 s. `timeout-minutes: 20` is a ceiling for a hung suite, not a duration. It is also bounded: the workflow's