Repository navigation
TEST 116
Use a controllable transport and fake monotonic clock to simulate successful sequential frames, second-frame timeout, slow pre/postflight, transient transport failure, malformed output, identity mismatch, retry exhaustion, cancellation during a request/backoff, and a server that may continue after client timeout. Supply missing/negative/infinite policy values and required resource controls that the endpoint cannot enforce. Test shared-daemon residency with another client and with no proof of exclusive ownership. Make failure finalization itself fail after an earlier error.
Invalid policies fail before inference; no request timeout or backoff extends the overall deadline. Request/retry counts stay within policy and no new work starts after cancellation. Nontransient invalid evidence/identity/output is not retried with weaker settings. Deadline/cancellation yields incomplete non-success state with sanitized cause, never configuration validity. Requested residency stays bounded; no shared-daemon stop/reconfiguration, model deletion, or unowned forced unload occurs. Unknown server completion remains explicit rather than claiming cancellation of server computation. Cleanup does not mask the original failure or expose raw evidence. Executed regression artifacts and limits are recorded in REQ-114; these fake-clock/transport cases do not load a model or change shared CPU/GPU/service settings. A separately authorized public smoke is not substituted for these failure-path tests.