mirror of
https://github.com/logos-blockchain/logos-execution-zone-module.git
synced 2026-07-09 03:59:41 +00:00
f4245bd593
The execution-zone doc-test is intermittently red (~1 in 3 on the GitHub runners): the module loads (daemon reports "loaded"), then on the very next IPC call it reports "not_loaded" and every method fails — even name()/version(), which touch no FFI. The module subprocess dies right after load. It does not reproduce off the hosted runners (verified: ~700 module loads + 24 parallel real-doc-test samples on x86-64 Linux under heavy contention, all green), so the signature has to be captured in CI. This adds a self-contained, opt-in probe workflow (manual dispatch or the `crash-probe` PR label) that loops the real doc-test until the first failure, then uploads the daemon logs.txt — kept via --keep-workdir and captured AFTER the failure (the spec only cats it before load), with RUST_BACKTRACE=full — plus kernel dmesg and a coredump backtrace (gdb on Linux / .ips crash report on macOS) as the lez-crash-<os> artifact. Diagnostics only; does not touch the production doctests.yml. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>