Skip to content

fix(iss-2611060835372141): TestASilentAgentIsAHangWithRecovery sets a 5-second runner limit that also covers the ordinary launches after the hang (… - #1491

Queued
REPPL wants to merge 5 commits into
mainfrom
build/run-2611080034521416-lane-1
Queued

REPPL wants to merge 5 commits into
mainfrom
build/run-2611080034521416-lane-1

Conversation

@REPPL

@REPPL REPPL commented Nov 11, 2026

Copy link
Copy Markdown
Collaborator

This pull request fixes iss-2611060835372141 ("TestASilentAgentIsAHangWithRecovery sets a 5-second runner limit that also covers the ordinary launches after the hang (…") by its remedy. The implement loop built it in run run-2611080034521416 as lane-1, and wrote this text from the run's records.

  • Branch build/run-2611080034521416-lane-1, from dd4fbf7 to 9c73a4e.
  • Validation round 5 at 9c73a4e passed: ruthless-reviewer SHIP (reviewer 0 at middle (anthropic/claude-opus-5-5)), ruthless-reviewer SHIP (reviewer 1 at below (anthropic/claude-sonnet-5-5)), security-reviewer APPROVE (reviewer 0 at middle (anthropic/claude-opus-5-5)), security-reviewer APPROVE (reviewer 1 at below (anthropic/claude-sonnet-5-5)).
  • It resolves iss-2611060835372141, fixed by a1def8d.

Resolves: iss-2611060835372141
Assisted-by: abcd:dev
Assisted-by: Claude:claude-opus-5-5
Assisted-by: Claude:claude-fable-5-2

REPPL added 5 commits November 8, 2026 00:45
TestASilentAgentIsAHangWithRecovery set a five-second runner limit for
the whole drive, so the launches after the hang (the judge's and the
retried implementer's) ran under it too, and a loaded machine could kill
one and fail the check.

The test now drives in two runs. The first, under the 200ms hang limit,
ends at its bound once the hang has taken its line of the script. The
second takes the lane up again under the ordinary five-minute limit and
lands it. A transcript store of the test's own records the limit every
finished launch ran under and requires it to be the ordinary one.

Assisted-by: Claude:claude-opus-5-5
…since the lane's base

The implement loop merges main at 672900a into lane-1 of run-2611080034521416, because main moved since the lane's base; it never rebases, so every judged commit stays reachable.

Assisted-by: abcd:dev
TestASilentAgentIsAHangWithRecovery bounded its first run, the one under
the 200ms hang limit, at one hour. A hang killed before it advances the
script's count is launched again as a hang, and each such kill costs the
run a wait on its outage clock: 30s, 30s, 1m, 5m, 10m, then an hour. Six
in a row, which a loaded machine can produce, reached the bound with the
count unmoved and failed the check.

The first run is now bounded at thirty days, as the drive was before it
was split. Only the script's count ends it, by moving the clock to the
bound.

Assisted-by: Claude:claude-fable-5-2
…since the lane's base

The implement loop merges main at 3499ff5 into lane-1 of run-2611080034521416, because main moved since the lane's base; it never rebases, so every judged commit stays reachable.

Assisted-by: abcd:dev
The implement loop's landing for iss-2611060835372141: resolved iss-2611060835372141 with a1def8d.

Resolves: iss-2611060835372141
Assisted-by: Claude:claude-opus-5-5
Assisted-by: Claude:claude-fable-5-2
@REPPL
REPPL enabled auto-merge November 11, 2026 05:43
@REPPL
REPPL added this pull request to the merge queue Nov 11, 2026
Any commits made after this event will not be merged.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant