mirror of
https://github.com/DeusData/codebase-memory-mcp.git
synced 2026-11-12 09:47:20 +08:00
Martin Vogel
54dd5ad781
Two corrections. First, removing the CI job while keeping the compose service and the local bindings left the ladder carrying a lane CI did not have — the venue asymmetry the unification work exists to prevent. The lane now lives in both venues again. Second, and the reason the removal was wrong: the evidence behind it was entirely from the LOCAL arm64 container, while the job that got deleted would have run on x86-64. MSan's shadow and stack handling are materially better supported on x86-64, so the thread-stack overflows that drove the exclusions may well be architectural. I never tested the architecture CI uses, and the local ladder cannot emulate it faithfully — so 'it cannot run in CI' was an inference from the wrong platform stated as a fact. The CI leg therefore runs with MSAN_EXCLUDE="" — no exclusions — so the first run settles the question with real evidence on the real architecture. The script's exclusion list stays as the LOCAL default, documented as such. An accepted local/CI divergence for this lane specifically. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>