Files
codebase-memory-mcp/tests/windows
Martin Vogel 045e1aa688 test(windows): keep the extended-path machinery in the non-ASCII guard
pr-smoke was green but test-windows-guards failed, and the shape of the failure
named the cause:

  [PASS] non-ascii/latin1_accents  nodes=12 edges=21 definitions=5
  [FAIL] non-ascii/cyrillic        nodes=None edges=None definitions=None

ASCII and latin1 pass, Cyrillic does not -- latin1 survives a Western ANSI code
page and Cyrillic does not. But the product code was never the problem: the
wide-path helpers (win_utf8.h, runtime.c extended paths) were KEPT. I had
reverted this test to a base that predates them, so it lost windows_extended_path()
and the explicit `executable=` argument to subprocess.run. With
lpApplicationName NULL, CreateProcess applies the legacy MAX_PATH limit while
deriving the module name from the command line, so on CI's long guard-bundle
path the process never started and every count came back None.

Same mismatched-base class as the package wrappers: production kept the fix, its
test was reverted past it.

Restored from main and adapted rather than dropped -- it still covers
extended-length publication AND non-ASCII indexing. Only the sidecar
assertions are gone (one self-contained file to publish now), and the probe
uses --version instead of the removed --verify-runtime-assets.

Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
2026-08-09 18:46:05 +02:00
..