| commit | ab89a6e4981a2629b818609e511a850740d611cf | [log] [tgz] |
|---|---|---|
| author | Benjamin Peterson <bp@benjamin.pe> | Thu Aug 22 12:46:12 2019 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Aug 22 12:47:12 2019 -0700 |
| tree | 3f0e385c335b35649420a71e98054426072baad8 | |
| parent | 697d219526bffbecd29f29b402c9122ec5d9f2ee [diff] |
Always print the gRPC status code when it's not okay. Sometimes a failed grpc::Status doesn't have a message, in which case Bazel can log unhelpful messages like "Could not interrupt server ()". We should always log the Status's error code. C++ gRPC doesn't provide a public API to convert a grpc::StatusCode enum value to a string (https://github.com/grpc/grpc/issues/17969), so the numeric code is just going to have to do for now. Closes #7380. PiperOrigin-RevId: 264897070
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds 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:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.