commit | 68bc0bb365906f29d22561819e8db6b98c44c482 | [log] [tgz] |
---|---|---|
author | mstaib <mstaib@google.com> | Tue Mar 28 21:05:38 2017 +0000 |
committer | Philipp Wollermann <philwo@google.com> | Wed Mar 29 14:22:03 2017 +0200 |
tree | 5cd09ac3844a0fcd594c8e4863f6debffa2f387e | |
parent | 1cb9a012a73d6adfc0027099b5f3bd94784cc300 [diff] |
Catch cases where exec fails before WaitForCompletionCommand starts. It's possible for cases to happen where the BlazeCommandDispatcher fails before starting the WaitForCompletionCommand. In these cases, the test's command state handoff will never take place because no command state will be created to be handed off (obviously). This means that runIn will wait forever. Instead, if the command completes and the command state has still not been handed off, set an exception into the command state so that the test will fail without further troubles. RELNOTES: None. PiperOrigin-RevId: 151495494
{Fast, Correct} - Choose two
Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google‘s software, and thus it has been designed to handle build problems present in Google’s development environment, including:
A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.
An emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.
Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.
Find more background about Bazel in our FAQ.