| commit | ae5329809868071387fb76bdd60fbb0c921bc33c | [log] [tgz] |
|---|---|---|
| author | Googler <wyv@google.com> | Thu Aug 11 08:20:13 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Aug 11 08:21:34 2022 -0700 |
| tree | 48ec8ac5c4827c5648b3e8f73aee5b8a94426dac | |
| parent | e5a70a8500c57fa46f49835810477befdae29a16 [diff] |
Update googletest to 1.12.1 https://github.com/bazelbuild/bazel/commit/3469784a4935c91b4ac22bcfed6be52e6dfec878 caused many projects in our downstream pipeline to start failing, including Bazel itself: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2580#01828ab1-c309-4bc2-9a9a-46713d8fed98 For Bazel itself, the main culprit seems to be googletest v1.10.0 which was still using the old aliases. The newest versions of googletest fixed this (https://github.com/google/googletest/commit/5c08f92c881b666998a4f7852c3cf9e393bf33a7) For other projects, we'll just have to wait until they catch up. PiperOrigin-RevId: 466958093 Change-Id: I1679db1c2106fc54770445cda30bb7a417f8183f
{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
