commit | d345cf92670a2c15bd16102dc5e15c159c3bdcb7 | [log] [tgz] |
---|---|---|
author | Ulf Adams <ulfjack@google.com> | Tue Mar 07 10:04:53 2017 +0000 |
committer | Vladimir Moskva <vladmos@google.com> | Tue Mar 07 10:48:40 2017 +0000 |
tree | fb24d21e2e395fbe5a9c87f86c539c2064b3e27a | |
parent | 9d3f989a433e6f7287c65ddd076a2e92b1778e4b [diff] |
StandaloneTestStrategy sets the full list of outputs on the test spawn All spawn strategies already treat all normal outputs as optional. Bazel checks at the action level whether all action outputs are created, but does not check at the spawn level. Spawn.getOptionalOutputs is therefore unnecessary, and removed in this change. The only place where this was set was in StandaloneTestStrategy, which now specifies the full set of outputs, which is now computed by TestRunnerAction. The internal test strategy implementations are also updated in this change. While I'm at it, also remove the use of BaseSpawn and use SimpleSpawn instead. This may go some way towards fixing #1413 and #942. -- PiperOrigin-RevId: 149397100 MOS_MIGRATED_REVID=149397100
{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.