| commit | 9520447f0b743e70f81489b87235c0b77ba51366 | [log] [tgz] |
|---|---|---|
| author | Lukacs T. Berki <lberki@google.com> | Wed Jul 20 12:27:00 2016 +0000 |
| committer | John Cater <jcater@google.com> | Wed Jul 20 15:01:42 2016 +0000 |
| tree | dedbc57574e6e7033af09884c06a533055bc72af | |
| parent | 3bed4af4f27bbd22b5531454095f0eda30bfac9f [diff] |
Fix various breakages in Windows process handling that creeped in because we weren't actually running the test: - Call TerminateProcess() only if the process handle is still open - Update the tests so that they expect a return value of 0 when reading a stream from a non-existent process Fixes #1538 . -- Change-Id: I4de28abbba2e2e89f285d7b8fb75bcd9af345f14 Reviewed-on: https://bazel-review.googlesource.com/4100 MOS_MIGRATED_REVID=127935621
{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.