deploy.yml: a superseded run is a skip, not a failure (#167) #217

2026-10-04T18:40:40-04:00

logan commented

2026-10-04 18:40:40 -04:00

Runs 1139 and 1144 (2026-10-04) were reported as failed deploys. Both runs printed SUPERSEDED= on the VM and touched nothing, but ssh still returned exit 1. Under bash -e the step died before the SUPERSEDED check could run.

Now the step saves the ssh exit status, checks SUPERSEDED first, and only then fails on a non-zero status.

Tested locally with a stub ssh: a superseded run exits 0, and a real ssh failure still exits non-zero.

Still open: why the remote exit 0 comes back as 1. It may be ~/.bash_logout on the VM.

🤖 Generated with Claude Code

Runs 1139 and 1144 (2026-10-04) were reported as failed deploys. Both runs printed `SUPERSEDED=` on the VM and touched nothing, but ssh still returned exit 1. Under `bash -e` the step died before the SUPERSEDED check could run. Now the step saves the ssh exit status, checks SUPERSEDED first, and only then fails on a non-zero status. Tested locally with a stub ssh: a superseded run exits 0, and a real ssh failure still exits non-zero. Still open: why the remote `exit 0` comes back as 1. It may be `~/.bash_logout` on the VM. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

logan added 1 commit 2026-10-04 18:40:41 -04:00

deploy.yml: a superseded run is a skip, not a failure (server-26#167) 73d692109c

The remote 'exit 0' came back as ssh exit 1 on the VM, and under bash -e
the step died before the SUPERSEDED check ran (runs 1139, 1144). Capture
the ssh status, check SUPERSEDED first, then fail on a non-zero status.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

logan merged commit dc1df72c86 into main

2026-10-04 18:41:32 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: logan/server-26#217