phase-merge can read the forge before a recovery push moves the pull request head, and spends a retry on the old red #594
Labels
No labels
agent-ready
bug
contract
documentation
duplicate
enhancement
good first issue
help wanted
invalid
needs-human
needs-input
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
iterative-works/iw-cli#594
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Found during IW-491.
After a recovery push,
phase-mergemay read the forge before the forge has moved the pull request head to the pushed commit. The read then returns the old head and its red verdict, andphase-mergecounts that as a failure of the new head and spends a retry.PROPOSED FIX. Before judging a reading, compare the pull request head with the local pushed sha. When they differ, the reading is not yet about the pushed commit: wait and read again, and do not spend a retry.
Closed as a duplicate of #601, which takes this defect and three others as one investigation on one branch. This one is phase 3 there.
The four share a cause: the card and the CI reading do not agree on which head they speak about. Fixing them apart would read the same code four times.