| commit | 7718ea301b364e84481bc2f5ff22d5ffc4841fdc | [log] [tgz] |
|---|---|---|
| author | Googler <pzembrod@google.com> | Wed Oct 09 05:21:25 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 09 05:22:33 2024 -0700 |
| tree | 9a0f202fb308ff4d2a40226efccb8a77af3d3652 | |
| parent | 8e1bf92feba894b8888c5eaf38c2fd1b8e693d58 [diff] |
Automated rollback of commit 8b19650b5817a80fce115b3ede20e92a409eabd6. *** Reason for rollback *** After the root cause for b/356561371 has been identified, and the fix unknown commit is in, this blunt mitigation is no longer needed. Independent of this, investigations and considerations on how to prevent this in the future are still ongoing. *** Original change description *** Blunt mitigation for blaze crashing with includes_scanning error: Adding retries for the 2 error modes. The as yet not understood root cause of this crash must be an unhandled race condition where a *.blaze-grepped_includes_CPP file is read before it is present and fully available. The two fixes are: 1. Waiting for the file to exist if it doesn't. This wait is very cheap, and it covers the majority of error cases. 2. Retry reading the file should an IOError occur while reading the file. This is... *** PiperOrigin-RevId: 683997262 Change-Id: I6d1f612b1e7ffa146afec8d517e5f28145f12241
{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
