From 9e05dbf5a7c258092affcfe4fe26a39af5575b69 Mon Sep 17 00:00:00 2001 From: Sergei Poljanski Date: Fri, 13 Nov 2026 03:15:31 +0400 Subject: [PATCH] docs: runner 13 marks the self-replacing run as failed Under runner 13 the run that recreates the runner ends as failed, not cancelled (run 450); say so, and where its log stops, so it is not mistaken for a real failure. Assisted-by: Claude:opus-5-5 --- ansible/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/ansible/README.md b/ansible/README.md index 5cf965c..784bfcf 100644 --- a/ansible/README.md +++ b/ansible/README.md @@ -91,7 +91,9 @@ variable, let the pipeline apply it, then remove the old volume. Renovate PRs. Applying either one recreates the runner while it runs the very job that applies it: -- that run ends as *cancelled* after everything else has been applied, +- that run ends as *failed* (runner 13; *cancelled* on older runners) + after everything else has been applied, its log stopping in the + forgejo_runner role, and its job container stays behind on asxpio-services (`docker ps | grep FORGEJO-ACTIONS-TASK`); remove it; - the next run confirms the result. The workflow only triggers on