| commit | 034a2815a1e18be5c8b36c6a78f44bb849dff437 | [log] [tgz] |
|---|---|---|
| author | Chi Wang <chiwang@google.com> | Tue Feb 28 19:13:21 2023 +0100 |
| committer | GitHub <noreply@github.com> | Tue Feb 28 18:13:21 2023 +0000 |
| tree | 1a8bfc640bf2dcdde4579b027a89959f9195d660 | |
| parent | 938e34823206a2644d538ba655d20ac553352975 [diff] |
Report background download for BwoB (#17619)
When building without the bytes, downloads can happen when Bazel need to fetch inputs for local actions, download outputs of toplevel targets, and etc. The downloads happen silently at the background.
This PR makes output downloads of toplevel targets visible to the UI.
For downloads during the build, the UI looks like:
```
[2 / 5] 2 actions, 1 running
[Prepa] Executing genrule //:foo
Executing genrule //:bar; 2s
Fetching bazel-out/darwin-fastbuild/bin/baz; 50.8 MiB / 1.0 GiB; 4s
```
For downloads after build is completed, the UI looks like:
```
INFO: 2 processes: 1 remote cache hit, 1 internal.
INFO: Build completed successfully, 2 total actions
Fetching bazel-out/darwin-fastbuild/bin/baz; 48.8 MiB / 1.0 GiB
```
Fixes https://github.com/bazelbuild/bazel/issues/17417.
Closes #17604.
PiperOrigin-RevId: 512934756
Change-Id: I502489420ab9b84efb74ceabbe3dd4cb4a7a62e2{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
