| commit | 1b9e2fbc9021e24ff45af63e7aaa6e1547c35c24 | [log] [tgz] |
|---|---|---|
| author | larsrc <larsrc@google.com> | Thu May 06 07:46:30 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu May 06 07:47:59 2021 -0700 |
| tree | 776d990268e57ee31a746c9b5434ba1cfd55eac9 | |
| parent | b5bfcc1ed0388fb5f0e3924d8fd33ea1bb3db0e1 [diff] |
Add more debugging output to dynamic execution. We can't get null from runLocally(), that would crash, but runSpawnRemotely() does not have such a check. I'm not making it fail on this, as I want to see if this is where the occasionally neither-branch-finished crash comes from. RELNOTES: None. PiperOrigin-RevId: 372341493
{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:
See CONTRIBUTING.md
