commit | b03bb844b10d5d0d29f5859293e91b5bd739c64f | [log] [tgz] |
---|---|---|
author | jhorvitz <jhorvitz@google.com> | Wed Jan 05 12:37:10 2022 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Jan 05 12:38:46 2022 -0800 |
tree | f35765b0f41a340c237fc0bef1e494ed060f69b1 | |
parent | 17e84b37f33ea117ac375c078a7f2a18d1e11765 [diff] |
Move the crash terminating callback to `SerializationContext` instead of passing it in. I'm guessing there was previously a circular dependency issue that prevented `SerializationContext` from depending on `BugReport`. PiperOrigin-RevId: 419890256
{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