Skip to content

[runtime] Harden chain test diagnostics#33

Merged
GsCommand merged 1 commit intomainfrom
codex/fix-failing-chain-test-in-runtime-signing.test.mjs
Mar 20, 2026
Merged

[runtime] Harden chain test diagnostics#33
GsCommand merged 1 commit intomainfrom
codex/fix-failing-chain-test-in-runtime-signing.test.mjs

Conversation

@GsCommand
Copy link
Contributor

Motivation

  • The full chain clean->summarize->classify test could hang for ~100s and produce opaque fetch failed failures, making CI diagnostics slow and unclear.
  • Make chain failures explicit, fast, and actionable without changing runtime logic or behavior.

Description

  • Replace the test-local runVerb helper with an abortable fetch that times out after 10s, reads response bodies, turns non-2xx responses into HTTP <status>: <body> errors, and wraps failures with runVerb(<verb>) failed: <cause> for clear verb-level context.
  • Convert the clean -> summarize -> classify flow into strict step-by-step assertions that validate the presence of cleaned_content, summary, and the final receipt, and emit CHAIN FAILURE DEBUG: plus the error on failure.
  • Reduce the test timeout to 20s by passing { timeout: 20000 } to the failing test so CI stops early on hangs.
  • Log the full verification result with console.log("VERIFY RESULT:", verifyJson); before the final assertions to surface /verify?schema=1 output in CI logs.

Testing

  • Ran node --test runtime/tests/runtime-signing.test.mjs and the test file completed with all tests passing (10/10).
  • The modified test exercised the chain path and printed the VERIFY RESULT payload, confirming the verification checks and producing actionable output when failures occur.

Codex Task

…g test fail fast with explicit per-step errors instead of hanging on opaque fetch failures.\nContract impact: none
@GsCommand GsCommand merged commit 297b818 into main Mar 20, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant