| commit | 8f9fb8d6f7ef7bd1c52b8ad1974959a91cd1e6d2 | [log] [tgz] |
|---|---|---|
| author | Googler <tanzhengwei@google.com> | Thu Feb 08 04:06:31 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Feb 08 04:08:27 2024 -0800 |
| tree | 063636710df7b29a80902af9808db34e0154529b | |
| parent | c3c8f15a78a865c72cc055d986a85cbaf36cd93a [diff] |
Introduce new flag --experimental_worker_use_cgroups_on_linux that uses cgroups to track memory usage for singleplex workers (on Linux) without imposing any hard limits. TODOs: - Figure out how to get around cases where Blaze is put automatically put in a root cgroup as a consequence of the session it was run from (e.g. ssh). One possibility is using `systemd-run`. RELNOTES: Introduce new flag --experimental_worker_use_cgroups_on_linux that uses cgroups to track memory usage for singleplex workers (on Linux). PiperOrigin-RevId: 605270861 Change-Id: I6c6cffb0568de7d4ccfbc4624c579bc3d64fadb4
{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
