tree 179adced487f67f506c46daa6115cc84cc898876
parent 02b4dd71b76e23949307004b5c6319afb073b302
author Fabian Meumertzheim <fabian@meumertzhe.im> 1729776613 -0700
committer Copybara-Service <copybara-worker@google.com> 1729776701 -0700

Use backslashes in executable paths when remotely executing on Windows

`.bat` scripts can only be executed on Windows when their paths use backslashes, not forward slashes. For this reason, local execution carefully replaces forward slashes with backslashes in the executable of a `Spawn` when executing on Windows.

This commit adds equivalent logic for the case of remote execution on Windows from any host:
* Remote execution replaces forward slashes with backslashes in the first argument when executing on Windows.
* Most calls to `PathFragment#getCallablePathString` are replaced with the new execution platform aware `getCallablePathStringForOs`. This affects test actions, in which various wrappers execute different executables (e.g. `--run_under` targets) and thus can have Bazel-controlled executable path strings in locations other than the `argv[0]`.

Fixes #11636

Closes #23986.

PiperOrigin-RevId: 689357323
Change-Id: Ifb842babc02c6d741d3b45914a5bf5c032204e2b