bazelbuild / bazelbuild/bazel

Cannot run tests on windows RBE from linux host due to missing files

Open
#29,948 3 comments 0 reactions 0 assignees View on GitHub
team-Configurability team-Remote-Exec type: bug
Dominant language
Java
Stars
25.8k
Forks
4.6k
Avg merge
2d 20h
Merged PRs (30d)
72

Description

### Description of the bug:

When trying to test a `py_test` target on Windows RBE from a linux host, we get the following errors:

```
ERROR: : Testing failed: missing input file '@@bazel_tools//tools/test:tw.exe'
ERROR: : Testing failed: missing input file '@@bazel_tools//tools/test:xml.exe'
ERROR: : Testing failed: 2 input file(s) do not exist
```

Looks like these 2 binaries are prebuilt and only bundled with the Windows build of bazel:
https://github.com/bazelbuild/bazel/blob/818c4c8de8b5ff7cd41cc25f3b2f7f61dac82432/tools/test/BUILD#L51

### Which category does this issue belong to?

CLI

### 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?

linux (windows RBE)

### What is the output of `bazel info release`?

9.1.1

### 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` ?

```text

```

### 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?

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with tools/test/BUILD, especially the entries for tw.exe and xml.exe, and reproduce a py_test target on a Linux host using Windows RBE. Trace how these prebuilt test binaries are packaged and made available to the remote test action; done means the Windows RBE test no longer reports either file as missing.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, cli, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.