Option to not download action/test stdout/stderr
- Dominant language
- Java
- Stars
- 25.8k
- Forks
- 4.6k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 75
Description
### Description of the feature request:
According to this [StackOverflow answer](https://stackoverflow.com/questions/77262480/how-to-keep-bazel-from-downloading-failing-test-logs), there is currently no way to prevent bazel from downloading action stdout/stderr. I'd like to be able to not download these files, as when using RBE they should still be available and announce-able via BES.
### Which category does this issue belong to?
_No response_
### What underlying problem are you trying to solve with this feature?
I was looking for this after a misbehaving set of tests were emitting O(100's MB) of output to stdout, and bazel in automation was downloading these files and filling up the CI worker's local storage.
We run against an RBE environment and pass `--remote_download_outputs=minimal` in order to keep the requirements of the CI worker executing bazel low; in this same spirit, I'd like to limit the downloading of stdout data (foregoing the ability to log that data in CI, of course) to increase the stability of automation in the face of poorly-behaving actions.
### Which operating system are you running Bazel on?
linux
### What is the output of `bazel info release`?
release 6.3.2
### 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 master; git rev-parse HEAD` ?
_No response_
### Have you found anything relevant by searching the web?
_No response_
### Any other information, logs, or outputs that you want to share?
I thought perhaps `--test_summary=none` would allow bazel to elide these downloads, but that was not the case.
Contributor guide
Research direction
Start by tracing how Bazel handles action and test stdout/stderr with --remote_download_outputs=minimal and how --test_summary=none affects downloads. The change is complete when users have an option to avoid downloading these outputs while they remain available through BES, with behavior documented and covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd, distributed-systems, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100