Ivan FB 0d1abb4ced

fix(tests): ignore non-terminal RET_STALE_WARN in testCallback ...

The shared result callback treated every code as an answer, so the 5s
stale ping fired by the slow arm+ASan runner during the 50k-ref-alloc
handler woke waitCallback with retCode=3 and let the test tear the
context down while the handler was still running -- which in turn made
destroyFFIContext err and left the event thread firing on a torn-down
signal (the UBSan fireSync null deref). Honour the same contract the
generated C/C++/Rust trampolines now follow: a progress ping is not a
reply. Tests asserting on the pings use staleCallback instead.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-14 14:31:42 +02:00

..

bench

feat(ffi): sharded MPSC request ingress (alternative to lock-free #98) (#101)

2026-06-27 19:08:10 +02:00

e2e

feat: CBOR-free abi=c C bindings (-d:targetLang=c_abi) (#109)

2026-07-06 13:48:08 -03:00

unit

fix(tests): ignore non-terminal RET_STALE_WARN in testCallback

2026-07-14 14:31:42 +02:00