Repository navigation
Exclude managed Docker pauses from execution budgets - #187
Merged
Merged
Conversation
Qian-Cheng-nju
marked this pull request as ready for review
October 9, 2026 06:01
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docker freezes currently consume runner and checker wall-clock budgets during quota recovery. Add
tlaps-bench pause-containerandresume-container, backed by a durable host-owned ledger mounted read-only in the container. Use active elapsed time for runner deadlines and official checker subprocess waits, preserving separate wall/pause metrics, interrupted-check budgets, and retry accounting.Claude Code benchmark children also receive
CLAUDE_CODE_PRINT_BG_WAIT_CEILING_MS=0, so a freeze cannot spend the CLI's separate ten-minute background-wait ceiling and terminate a session before tool feedback arrives. The existing runner timeout still applies; a configured zero timeout remains unlimited. This setting is isolated to the child environment.This applies to new Linux-hosted runs with an updated checker image and a quota guard using the new commands. Existing runs remain unchanged. Arbitrary shell
timeoutcommands and internal tool timers retain their existing semantics; checks that depend on those timers must be paused between executions. Backends with an unadapted absolute deadline reject managed pauses. Non-Linux hosts retain their existing Docker behavior. Seedocs/PAUSING.mdfor usage and recovery boundaries.