Recognize managed test wrappers in chained test reports - #762
Conversation
|
Review verdict: Approved The clause-level managed-wrapper recognition is correctly scoped: it preserves the wrapper and memory-output exemptions while recursively validating leading assignments and inner commands, continues validating surrounding shell clauses, and falls back to ordinary validation for malformed wrapper syntax. The focused regression coverage exercises both supported wrapper forms, multiple chain operators, structured and legacy reports, outside paths, live targets, and malformed options. GitHub PR checks are passing. -- OpenAI Codex: gpt-5.6-sol (medium) |
|
Review verdict: Approved Verified the local diff at head 0ed9023 in the assigned checkout. Factoring the wrapper contract into -- Anthropic Claude: claude-opus-5 (medium) |
|
PR review round 1 reconciliation: settled reviewers: Claude, Codex. Finalization continues after reconciliation. |
|
Reviewers approved PR #762; watching GitHub checks in the foreground. No coder or reviewer agents will run while checks remain pending. -- coding-review-agent-loop |
Summary
Recognize managed
agent-loop run-testsinvocations within parsed shell clauses, not only at the beginning of an entire test report.Why
An interrupted coder follow-up on #757 reported:
The guard incorrectly treated the absolute wrapper executable as a test outside the assigned checkout. The same managed invocation was already accepted without the preceding
pwdandgit statusclauses.Changes
&&,;, and||chains, repeated wrappers, Python-module wrappers, legacy backticked reports, and invalid targets/options.No installed tool configuration or reviewer approvals are changed.
Validation
python3 -m pytest tests/ -q --tb=short: 2,715 passed in 138.62 seconds.git diff --check: passed.test_runner_pty_timeout_is_opt_in_and_retains_combined_log. Its isolated rerun passed; no PTY/test-timeout code was changed.-- OpenAI Codex