bazelbuild / bazelbuild/bazel

`test.outputs` are downloaded on test failure, even when using `--remote_download_minimal`

Open
#26,043 4 comments 0 reactions 0 assignees View on GitHub
P3 team-Remote-Exec type: bug
Dominant language
Java
Stars
25.8k
Forks
4.6k
Avg merge
2d 18h
Merged PRs (30d)
75

Description

### Description of the bug:

When using `--remote_download_minimal` and a test passes, its `test.outputs` are not downloaded. But when the test fails, they are. They should instead only be downloaded if a `--remote_download_regex` matches them.

### Which category does this issue belong to?

Remote Execution

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

macOS 15.4.1

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

release 7.6.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

No implementation file or test is named. Start by reproducing the behavior with --remote_download_minimal and a failing test, then trace Bazel's remote-execution handling for test.outputs and --remote_download_regex; done means failed tests no longer download outputs unless the regex matches them.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.