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
..
2026-05-19 12:43:34 +02:00