Repository navigation
fix: keep a build alive when the job branch moves under it - #17
Merged
Merged
Conversation
Publishing the running state pushed once and failed the whole build if the branch had moved, which is how a healthy run died: the web app wrote a verdict to the same branch while the runner was starting, and the runner's push was rejected seconds later. The web app no longer writes there, but losing a build to a lost race is worth guarding against on its own, so the push rebases and retries. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0185X6NPgr1v2jXVVDnK5DmZ
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
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.
Publish running statepushed once and failed the entire build if the branch had moved. That is how run 31312424490 died:The run was healthy — it got a runner in 2 seconds, fetched the paper, and marked the job running. It only lost a race: the web app wrote a (wrong) dispatch verdict to the same branch eleven seconds earlier.
HumanStudy-Hub/humanstudy-hub-web#4 stops the web app writing there at all, which removes today's cause. This guards the step on its own merits — losing a whole build to a lost race is worth surviving regardless of who moved the ref. The push now rebases and retries up to three times, matching what
Commit job state and outputsalready does.🤖 Generated with Claude Code
https://claude.ai/code/session_0185X6NPgr1v2jXVVDnK5DmZ