fix(agent): a clone that lacks a fetched commit is cloned again before the job is refused #66
No reviewers
Labels
No labels
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Beanstalk!66
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/Beanstalk:fix/reclone-pr-head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
Tommy's Windows PC (nightly-124) refused the re-planned Longshot #910 with "the pull request's head is no longer e4609af92ac9", but e4609af92ac9 is #910's head on the forge. The fetch went through and the clone still lacked the commit. Earlier it lacked main's commit too ("main has no commit 02608169e638", after a git checkout killed with 0xC000013A), so the clone is damaged.
#59 clones again only when main's commit is missing. The PR's head was checked first, and its absence was taken as the PR having moved, so the re-clone never ran.
What changed
JobPipeline, for a PR job:git cat-file's words.Testing
dotnet build agent/App -c Release: 0 warnings.