Fix some skipped builds statuses never getting updated on Gitea - #549
Merged
Mic92 merged 2 commits intoJan 20, 2026
Merged
Conversation
Enzime
changed the title
Enzime
force-pushed
the
claude/fix-gitea-build-status-5GQ0K
branch
5 times, most recently
from
January 15, 2026 17:53
3a6c345 to
12cb713
Compare
When a build is cancelled via interrupt(), the cancellation is reported to Gitea but was not recorded in the failed_status database. This meant subsequent builds couldn't know which statuses needed updating. Now when a build is cancelled, all its pending status names are recorded in the failed_status database, allowing subsequent builds to properly update those statuses.
When a job would normally be skipped (output already in local store), check if its status was previously reported as failed/cancelled. If so, force schedule the build instead of skipping it. The build will succeed quickly since the output is already in the store, and the normal completion flow will send the success status to Gitea. This ensures that stale failed/cancelled statuses from previous builds get properly updated without needing special case handling.
Mic92
force-pushed
the
claude/fix-gitea-build-status-5GQ0K
branch
from
January 20, 2026 16:40
12cb713 to
35a5f3a
Compare
Mic92
enabled auto-merge
January 20, 2026 16:41
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/clan-core-changelog-26-01-2026/74813/1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To reproduce this issue on Gitea:
Settings>Webhooks> Edit Buildbot's webhook >Recent Deliveriesbuildbot/nix-eval(Evaluate flakes) step finishes, immediately select the"action": "synchronized"event and clickReplay this webhook.buildbot/nix-buildjob is green after the CI is finishedbuildbot/nix-build <flakeattr>checks will remain red and never get updated even if you clickRebuildon the overallbuildbot/nix-buildjobI've tested this on the Clan buildbot and it fixes the issue :)