| commit | 82317b5a69d8d32b515d6fce2d6729acc6f4f0e8 | [log] [tgz] |
|---|---|---|
| author | Googler <lberki@google.com> | Fri May 17 06:27:18 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri May 17 06:29:09 2024 -0700 |
| tree | 293f2bf4163988f1c378d1aa80402e57df1d4ba8 | |
| parent | 99f6ffbc81557b0f4fbdf8d74f8f3e15fc6df87f [diff] |
Make it possible to dump Skyframe memory at the end of a build. It works by passing the `--experimental_skyframe_memory_dump=json` command line option to build-like commands. If `--experimental_stream_log_file_uploads` is in effect, the file will be streamed to remote storage, if not, it'll be written to the output base to the eponymous file. Either way, its URI will be reported on the BEP as the file `skyframe_memory.json`. The format is the same as `bazel dump --memory=full,summary` and befitting an experimental option, is subject to change. This is modeled after the now-defunct `--experimental_aquery_dump_after_build_format` (that one will be deleted after this change is submitted) RELNOTES: None. PiperOrigin-RevId: 634743262 Change-Id: I3b5b4e13a252c7e6f7b4bad3067ea88753ff5931
{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
