giles
9b0f42defb
Some checks failed
Test, Build, and Deploy / test-build-deploy (push) Failing after 1m3s
Root cause investigation of WASM kernel timeout for tests 200, 207, 211: verified the kernel's __hs_deadline check IS firing correctly with the JS-side _testDeadline value. The tests were genuinely taking 60s+ because the (raise msg) inside hs-null-error! propagated up through the JIT continuation chain and triggered the slow host_error path (~34s per comment in the test runner override). The companion helpers hs-null-raise! and hs-empty-raise! already wrap their raise in (guard (_e (true nil)) (raise msg)) so the exception is swallowed before escaping. hs-null-error! was missing this guard — it just did (raise (str ...)). Fix: hs-null-error! now sets window._hs_null_error and uses the same self-contained guard pattern. The error message is still recoverable through the side channel, matching how the eval-hs-error override in the test harness expects to find it. Bumped hypertrace deadlines 8s→30s (modules-loaded JIT state has grown since the original 8s budget was set). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>