| commit | 77a002cce050e861fcc87c89acf7768aa5c97124 | [log] [tgz] |
|---|---|---|
| author | Brandon Jacklyn <brandonjacklyn@gmail.com> | Fri Nov 05 04:23:57 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Nov 05 04:25:00 2021 -0700 |
| tree | 43fabdbc8aeec3fa7b51e519e363e9da8279d19b | |
| parent | 917e15ea408e1d3d25574edbb466b39cfbcb61fe [diff] |
Remove DigestUtils.getDigestInExclusiveMode() now that SsdModule has … …been removed There used to be a cli flag --experimental_multi_threaded_digest which defaulted to true and therefore would not compute the file digest in exclusive mode unless overridden to false. When that flag was removed this code was accidentally left behind which instead causes bazel to always compute file digests in exclusive mode for all files larger than MULTI_THREADED_DIGEST_MAX_FILE_SIZE. This causes bazel to take 5-6x longer to 'check cached actions' in my org's builds, specifically increasing the time from 30 secs to 2 mins 30 secs for fully cached no-op builds. Fixes #14034 Closes #14231. PiperOrigin-RevId: 407790990
{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
