Repository navigation
Give Delivery's nested Markdown suites independent CI deadlines - #1409
Conversation
Delivery.test.md ran the nested summary-repair and progress-completion documents inside its own 300-second whole-launch budget, and on a slow Node runner the cumulative work reached that deadline (#1408). Each wrapper now lives in its own directly discovered suite with the 120-second adversarial deadline, keeping its Deno child command, authored case timeout and nested document unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Hosted measurement started on the exact source commit Fable returned only its five-hour quota notice before producing a review; its provider scope joined and all failed records are retained. The existing repository policy and prior user direction authorize the independent Codex |
|
Independent review: PASS on exact signed Reviewer: Codex The reviewer independently compared both moved wrappers/preambles and the unchanged nested documents against the base. All titles, variants, assertions and 120s/90s case allowances are preserved. Discovery, explicit 300s/120s document deadlines, fixture plugin/includes and Deno child execution were traced through the real runner. All nine candidate launch receipts match the reviewed source; focused formatting also passed. No blocking findings. Receipt SHA-256: Hosted measurement 44232626922, required CI and exact-head review of the eventual generated weights remain delivery gates. This source PASS does not claim merge readiness. |
|
Required source CI passed on reviewed The PR remains draft because the required full-corpus measurement 44232626922 is still running. Its complete generated weights, truthful measured-source provenance and final exact-head review/CI are still required. No incomplete measurement or source-only PASS is being treated as merge readiness. |
|
Measurement sequencing correction: run 44232626922 was deliberately stopped. It began before the pending journal PR #1402's added test file was included, so its corpus would be obsolete once that PR merges. All three measurement jobs were still running without a failure when cancellation was requested. Partial records/logs will be retained as historical evidence. The mandatory complete measurement will run after #1402 and #1407 merge and this PR is based on their actual final main. The resulting artifact must still pass same-source/run/attempt validation, supported reassembly, deliberate generated-file commitment and final exact-head review/CI. Source |
|
The cancelled measurement's preserved partial records had already completed all three affected suites on source
Delivery's document limit remains 300s; each extracted suite's document limit is 120s. Authored inner case limits remain unchanged. These completed individual-file measurements are retained evidence of bounded hosted execution; they do not establish a controlled total-runtime speedup. All three full-corpus records are explicitly |
Why
Delivery's Markdown suite exceeded its shared five-minute deadline on a slow Node CI runner, interrupting the final case after about 39 seconds of its 90-second allowance. Its earlier phases had also slowed; the saved trace does not demonstrate a blocked Prompt. Refs #1408.
What changes
The existing summary-repair and progress-completion groups become two independently discovered Markdown suites. Delivery keeps its 300-second document deadline. The new suites each use the existing 120-second adversarial suite class, while retaining their original wrapper and nested case timeouts.
How it works
CI discovers and shards
DeliverySummaryRepair.test.mdandDeliveryProgressCompletion.test.mddirectly. Their existing wrappers still launch the nested documents through the normal Deno fixture command under every outer runtime. Both suites are explicitly registered in the deadline map and discovery/launch regressions.How to verify it
29bfc884418892117ac664c36ad524e2c2aae649. Independent Codexgpt-6-astrareview: PASS on the same source revision, after the retained Fable quota-only refusal and documented provider reconciliation.Scope
The change reorganizes existing test groups and registers their existing deadline class. It adds no product API, timeout increase, dependency change or weaker assertion.
Generated or mechanical changes
Hosted corpus remeasurement is mandatory and pending. The first run was stopped because it excluded the new test file in pending #1402. After #1402 and #1407 merge, the supported workflow will measure the final rebased source, covering the settled corpus. Its complete assembled artifact will be committed deliberately with truthful source/run/attempt provenance; measurements will not be edited manually. Source review and passing focused tests do not waive this delivery work.
Risks and limitations
Local runtime/host versions differ from hosted CI. Source reviews are complete. Required CI passed on the reviewed source commit. Hosted measurement, the generated weights commit and final exact-head review/CI remain pending. The known timeout issue stays open until its correction and delivery evidence are complete.
Scope confirmation