ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Bazel
    • None
    • Build OnDeck
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Windows Bazel test runfiles can exceed MAX_PATH and fail before tests start or lose their golden data. Add a native Windows launcher that runs the original executable, preserves arguments and exit status, and captures timeout minidumps. The native entry passes arguments to PowerShell in a UTF-16 payload, preserving percent expressions and empty arguments. Resolve golden-data roots from the test environment, handle failed executable canonicalization and null GoogleTest/UCRT parameters, and preserve UTF-8 logs and fractional durations in `create_bazel_test_report.py`.

      Evergreen's Windows Bazel test command selects the native launcher and an explicit source-checkout golden-data root. A suite under `//src/mongo/unittest` includes the production launcher regression in unit-task target selection. The cross-toolchain default, remote-link policy, distro migration, and failed-test artifact collection remain in #63670's decomposed follow-ups.

            Assignee:
            Daniel Moody
            Reporter:
            Daniel Moody
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: