A verifier call with no answer fails that check, not the run
Found by a live run. One verify call generated 16,000 tokens without ever closing its JSON answer, hit the 600 s wall-clock limit, and ended the whole run. It happened twice.
- Output cap: every structured call is capped by
PIPELINE_MAX_OUTPUT_TOKENS(default 2048), so a runaway call stops in about a minute. - Narrower error:
ModelOutputError, a subclass ofLLMError, marks one failed call: out of time or tokens, or not JSON. An unreachable server or a client that stopped answering still raisesLLMErrorand ends the run. - Failed checks: a verifier call that fails this way is recorded as
CHECK_FAILEDand never counts as support. - Unverified claims: a claim that no verifier answered for gets
VERIFIER_FAILED. It is removed from the answer and counted in Limits. A real verdict from another check still decides the claim.
Tested:
- 230 tests pass, including tests for each case. ruff and pyright are clean.
- The live re-run completed. The two runaway checks were capped and reported in Limits, and the answer was produced.
🤖 Generated with Claude Code