CI: GTest filter not applied correctly on Windows PowerShell

[derekxmartin]

Problem

The CI script (scripts/ci.ps1) cannot reliably pass --gtest_filter exclusions to the GTest binary on Windows. PowerShell expands * as file globs and Start-Process doesn't reliably populate ExitCode.

Hanging tests that need exclusion

• QuarantineTest.* — SQLite file lock
• OOXML.DetectsVbaProjectBin — ZIP parser infinite loop on 1-byte vbaProject.bin
• X86Emu.* — long-running emulator tests

Attempted fixes

1. Start-Process -ArgumentList — * expanded as glob
2. cmd /c with escaped quotes — * expanded by cmd.exe
3. --gtest_flagfile — flag file written correctly but filter still not applied
4. Direct & $exe invocation — hangs on pipe output

Workaround

Run tests directly: .\build\Release\akesoav_tests.exe '--gtest_filter=-QuarantineTest.*:...'
Single quotes prevent PowerShell glob expansion when invoked interactively.

Root cause

Start-Process and cmd /c both expand wildcards before passing to the executable. The flagfile approach should work but needs further debugging.

🤖 Generated with Claude Code