ci: main looked red after #522, superseded push run cancelled by #532 (not a regression) #535

New issue

Closed

opened 2026-10-27 13:03:42 +00:00 by orion · 0 comments

orion commented

2026-10-27 13:03:42 +00:00

Collaborator

Finding

The red push CI on aed04243 (merge of #522) is a cancelled run, not a failure of #522.

#522 was merged at 12:33:03Z, #532 at 12:33:25Z, 22 s later.
ci.yml uses concurrency: group: ci-${{ forgejo.event.pull_request.number || forgejo.ref }} with cancel-in-progress: true, so both pushes share the group ci-refs/heads/main. The push of #532 cancelled run 2016 (on aed04243) after only commit messages, what the change touches and which runners exist had run. Those three passed, and no other job of run 2016 ever got a task.
Forgejo reports the cancelled jobs as failure in the commit status. That is why gates, tier A, bootstrap, archives and every other job look red on aed04243, including unrelated ones such as the VS Code extension. The images run 2017 (site:edge) for the same push was likewise cancelled by its edge concurrency group.
The PR run of #522 (run 2006) was green, including gates and tier A.

State

The push run 2019 on the current head 77259d30 (contains #522 and #532) is green. All ci / jobs passed, and the platform-gated ones were skipped as usual. The site:edge image of 77259d30 (run 2020) built successfully.

Live impact

None.

No release: the last tag is nightly-20261027 (142293fd, before #522). release.yml runs on tags only.
torb-site still runs cr.dmb.zone/torb/site@sha256:457578de… (pod started 2026-10-20, 0 restarts). torb.dev and torb.dev/play return 200.

Decision

No code change. Cancelling superseded main runs is intended: the head run covers every merged commit and saves runner time. Main is judged by its head commit, not by an intermediate commit whose run was cancelled.

## Finding The red push CI on `aed04243` (merge of #522) is a **cancelled run, not a failure of #522**. - #522 was merged at 12:33:03Z, #532 at 12:33:25Z, 22 s later. - `ci.yml` uses `concurrency: group: ci-${{ forgejo.event.pull_request.number || forgejo.ref }}` with `cancel-in-progress: true`, so both pushes share the group `ci-refs/heads/main`. The push of #532 cancelled run 2016 (on `aed04243`) after only `commit messages`, `what the change touches` and `which runners exist` had run. Those three passed, and no other job of run 2016 ever got a task. - Forgejo reports the cancelled jobs as `failure` in the commit status. That is why gates, tier A, bootstrap, archives and every other job look red on `aed04243`, including unrelated ones such as the VS Code extension. The images run 2017 (`site:edge`) for the same push was likewise `cancelled` by its edge concurrency group. - The PR run of #522 (run 2006) was green, including gates and tier A. ## State The push run 2019 on the current head `77259d30` (contains #522 and #532) is **green**. All `ci /` jobs passed, and the platform-gated ones were skipped as usual. The `site:edge` image of `77259d30` (run 2020) built successfully. ## Live impact None. - No release: the last tag is `nightly-20261027` (`142293fd`, before #522). `release.yml` runs on tags only. - `torb-site` still runs `cr.dmb.zone/torb/site@sha256:457578de…` (pod started 2026-10-20, 0 restarts). `torb.dev` and `torb.dev/play` return 200. ## Decision No code change. Cancelling superseded main runs is intended: the head run covers every merged commit and saves runner time. Main is judged by its head commit, not by an intermediate commit whose run was cancelled.

orion closed this issue

2026-10-27 13:03:42 +00:00

No labels

loop

ready

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

torbscript/language#535

No description provided.

Rows
Columns