Skip to content

Allow ten hours for GenPlan containers - #179

Closed
joshnroy wants to merge 7 commits into
codex/genplan-code-submissionsfrom
codex/genplan-container-timeout
Closed

Allow ten hours for GenPlan containers#179
joshnroy wants to merge 7 commits into
codex/genplan-code-submissionsfrom
codex/genplan-container-timeout

Conversation

@joshnroy

@joshnroy joshnroy commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • increase the GenPlan Docker wall-clock timeout from one hour to ten hours
  • allow $20 Claude runs to finish training and return to host-side evaluation

Why

The one-hour subprocess.run timeout can expire before a GenPlan run exhausts its model budget. The Docker client then exits while the container continues in the background, leaving training artifacts such as cost.json but preventing held-out evaluation and results.json from being written.

Verification

  • python -m py_compile src/robocode/utils/docker_sandbox.py
  • git diff --check
  • 19 focused GenPlan tests passed; 6 rollout tests could not start their multiprocessing manager under the restricted Codex sandbox

Stack

Stacked on #178.

@joshnroy joshnroy changed the title codex/genplan container timeout Allow ten hours for GenPlan containers Sep 2, 2026
@joshnroy
joshnroy force-pushed the codex/genplan-code-submissions branch from 5323bd1 to ff85c29 Compare September 2, 2026 14:12
@joshnroy

joshnroy commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator Author

Folded into #177 so Claude session reuse and the container wall-clock limit can be reviewed together as one runtime reliability change.

@joshnroy joshnroy closed this Sep 2, 2026
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