Repository navigation
Bound Void Trial retries and report causes per Arm - #1133
Merged
Merged
Conversation
This was referenced Oct 23, 2026
Closed
Merged
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.
Summary
Provider-limit pauses consume the fixed retry budget across resumes, including #1008's live-warning supervision. Existing Experiments retain their saved Void rules across runner upgrades. Host-kill and memory-cap causes require the outer launcher's evidence; the sandbox and cap launcher remain #1014's work.
Closes #1007
Evidence
After: all three exact probes pass. Permanent regressions are
an_agent_killing_its_own_harness_fails_without_a_retry,a_server_error_on_resume_after_trial_work_is_failed, andresuming_an_experiment_preserves_its_preexisting_void_rulesin the Experiment/Trial integration tests. The existing test rejecting an explicit Bar change also passes.After: focused regressions confirm a timeout stays failed and provider-limit attempts exhaust the Bar's three total attempts.
cargo checkandcargo fmt --checkpass. CI on the exact head passed the fullcargo testsuite, Clippy, formatting, Python, site and Console checks. The local affected-test selection passed all 43 site checks; its duplicate Rust run was stopped after CI passed, reusing that result asdocs/testing.mddirects.Test seams
thirdshift --trial): observable classification and artifacts from fake Harness failures.thirdshift experiment/thirdshift experiments): fresh retries, fixed Bar, paired drop-outs, per-Arm Void counts, causes and memory-cap findings.verdict::judge): existing paired drop-out and one-tenth threshold tests.Review coverage
Reviewed against
issue-977, pinned at105f581b6e2d6603594b08dce724c321c53a3480, through headb7fe9d0. Standards: 0 findings. Spec: 3 P2 findings, all reproduced and fixed with retained regression tests. Both axes read all 29 changed files since that fixed point, including the merged #1008 work and generated HTML. The PR against the updated base changes 14 files; all were read. No changed file was left unread and no generated output was excluded.Unaddressed findings
Merge Danger
Door: two-way
Blast Radius: Experiments
Changes Trial classification, retry accounting and saved Experiment views.
Built with codex · gpt-6.1-sol · xhigh