automerge: merge API repeatedly failing on igor.bot#290, never succeeds in window #322

New issue

Closed

opened 2026-07-02 17:01:35 +00:00 by igor · 0 comments

igor commented

2026-07-02 17:01:35 +00:00

Collaborator

Diagnosis

Starting immediately after the 11:54 self-update (4178b18 -> 9ec17d2), every tick emits a warning that the automerge merge API call fails on joshtronic/igor.bot#290. It recurs on three consecutive ticks (11:54, 11:56, 11:58) with no subsequent success before the window closed -- the PR is stuck, not self-healing. This is not covered by any open issue or recent commit subject.

Evidence

Jul 02 11:54:48 igor tick.sh[1853750]: [agent] warning: automerge: merge API failed on joshtronic/igor.bot#290
Jul 02 11:56:43 igor tick.sh[1855840]: [agent] warning: automerge: merge API failed on joshtronic/igor.bot#290
Jul 02 11:58:43 igor tick.sh[1857186]: [agent] warning: automerge: merge API failed on joshtronic/igor.bot#290

What "fixed" looks like

Either the automerge succeeds (PR #290 merges and the warning stops), or the harness surfaces why the merge API is rejecting (e.g. conflict, required check, permission) instead of a bare repeated merge API failed warning. A persistent failure across ticks should either back off with a diagnostic or escalate once, not silently retry forever.

service: agent.service
severity: medium
window: 2026-07-02 11:00-12:00 (filed by the hourly logwatch pass)

## Diagnosis Starting immediately after the 11:54 self-update (`4178b18 -> 9ec17d2`), every tick emits a warning that the automerge merge API call fails on `joshtronic/igor.bot#290`. It recurs on three consecutive ticks (11:54, 11:56, 11:58) with no subsequent success before the window closed -- the PR is stuck, not self-healing. This is not covered by any open issue or recent commit subject. ## Evidence ``` Jul 02 11:54:48 igor tick.sh[1853750]: [agent] warning: automerge: merge API failed on joshtronic/igor.bot#290 Jul 02 11:56:43 igor tick.sh[1855840]: [agent] warning: automerge: merge API failed on joshtronic/igor.bot#290 Jul 02 11:58:43 igor tick.sh[1857186]: [agent] warning: automerge: merge API failed on joshtronic/igor.bot#290 ``` ## What "fixed" looks like Either the automerge succeeds (PR #290 merges and the warning stops), or the harness surfaces *why* the merge API is rejecting (e.g. conflict, required check, permission) instead of a bare repeated `merge API failed` warning. A persistent failure across ticks should either back off with a diagnostic or escalate once, not silently retry forever. --- service: agent.service severity: medium window: 2026-07-02 11:00-12:00 (filed by the hourly logwatch pass)