mirror of
https://github.com/DeusData/codebase-memory-mcp.git
synced 2026-11-04 18:58:00 +00:00
Martin Vogel
f96ddf5f93
Running the lane to completion does not currently work: with three suites already excluded for thread-stack overflow it now dies with a plain SIGSEGV elsewhere. Wiring an auto-running job that cannot finish would be exactly the structurally-red lane O10 forbids, so the test-msan CI job is removed and the lane is documented as exploratory and local-only. What it IS worth, and why the infrastructure stays: every suite it does run is clean under MSan, including the C++ preprocessing path that justified building the instrumented-libc++ image in the first place, and it correctly identified one convincing-looking report as a mixed-build artifact rather than a bug. The image, the script, the compose service, the MSAN_ORIGINS and CBM_THREAD_STACK_MB knobs, and the full record of what was tried all remain, so picking this up is a continuation rather than a restart. The blocker is one problem, stated at the exclusion site: threads whose stacks are sized outside cbm_thread_create overflow under instrumentation, and the failure follows cumulative process state rather than any single suite's depth — which points at per-suite process sharding or finding that thread creator as the fix. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>