asxpi/iac
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: runner 13 marks the self-replacing run as failed
All checks were successful
deploy / ansible (push) Successful in 4m17s
Details

Browse source 
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
This commit is contained in:
Sergei Poljanski 2026-11-13 03:15:31 +04:00
commit 9e05dbf5a7
Signed by: asxpi
GPG key ID: 4F8851660FA4121B
1 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
ansible/README.md
View file

@ -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 Renovate PRs. Applying either one recreates the runner while it runs
the very job that applies it: 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 and its job container stays behind on asxpio-services
(`docker ps | grep FORGEJO-ACTIONS-TASK`); remove it; (`docker ps | grep FORGEJO-ACTIONS-TASK`); remove it;
- the next run confirms the result. The workflow only triggers on - the next run confirms the result. The workflow only triggers on