bazelbuild/bazel

Bazel send host-formatted paths to test-setup and generate-xml scripts

Open

#28067 opened on Dec 19, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (25,384 stars) (4,465 forks)batch import
P3area-Windowshelp wantedteam-Remote-Exectype: bug

Description

Description of the bug:

When running tests on a linux remote executor from a Windows host, I see spawns like this:

external\bazel_tools\tools\test\test-setup.sh
./cc_test

and

external\bazel_tools\tools\test\generate-xml.sh
bazel-out/x64_windows-fastbuild/testlogs/cc_test/test.log
bazel-out/x64_windows-fastbuild/testlogs/cc_test/test.xml
0
1

Which of course results in {"msg":"executable file external\bazel_tools\tools\test\test-setup.sh not found in $PATH: No such file or directory","level":"error","time":"2025-12-19T19:26:33.011523Z"}

The underlying executable is built correctly.

/Users/dzbarsky/Downloads/cc_test: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.0.0, not stripped

Which category does this issue belong to?

No response

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

No response

Which operating system are you running Bazel on?

Windows

What is the output of bazel info release?

release 9.0.0rc2

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

cc @fmeum

Contributor guide

Tech stack
javashell
Domain
build systemci cd
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understanding of Bazel remote executionFamiliarity with Bazel's test infrastructure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
The bug is that Bazel passes host formatted paths (Windows) to test setup.sh and generate xml.sh when running tests on a Linux remote executor. This suggests the path conversion for remote execution is not being applied to these scripts. Investigate how Bazel constructs the command line for test actions, focusing on the code that generates the paths for test setup and generate xml scripts. Key files to examine include src/main/java/com/google/devtools/build/lib/exec/ and related test runner code. Also check recent changes related to remote execution path handling. The issue mentions a spawn with backslashes, so look for any path normalization missing for the test scripts.