deploy-remote: prune stale pending state for retired services
A pending entry for frank-default-sightsound (FLM NPU endpoint retired 2026-09-11) survived in the dankclaw state store and made every --pending run exit 2 at the dispatcher before the Playwright e2e gate could execute. The pending pass now drops entries the target no longer allows into ~/.AGENTTRASH and keeps going. Behavioral seam test added.
This commit is contained in:
@@ -177,6 +177,17 @@ add_pending_services() {
|
||||
if [[ "$status" != deployed ]]; then
|
||||
# A pending service was intentionally skipped or its handler
|
||||
# failed. Retry it even when the checkout has not advanced.
|
||||
# But a pending entry for a service RETIRED from this target can
|
||||
# never be deployable: retrying it fails the whole run before
|
||||
# the e2e gate (the frank-default-sightsound lockout, found
|
||||
# 2026-09-17). Drop such entries into the host trash instead.
|
||||
if ! service_is_allowed "$service"; then
|
||||
local trash="$HOME/.AGENTTRASH/$(date +%Y%m%d)-retired-deploy-state"
|
||||
mkdir -p "$trash"
|
||||
mv -- "$state_file" "$trash/$service"
|
||||
echo "WARN: $service is retired on $TARGET; dropped its stale $status state to $trash" >&2
|
||||
continue
|
||||
fi
|
||||
SERVICES+=("$service")
|
||||
continue
|
||||
fi
|
||||
|
||||
Reference in New Issue
Block a user