| commit | acd4f07a1d5f5d588087e5918c6009d26150d57e | [log] [tgz] |
|---|---|---|
| author | Lukacs Berki <lberki@google.com> | Fri Jun 24 07:24:11 2016 +0000 |
| committer | Lukacs Berki <lberki@google.com> | Fri Jun 24 08:12:39 2016 +0000 |
| tree | 068004165899a08a8773ca9622ded4398c8ed830 | |
| parent | 33d7bdb12541b2516d9798eb91df3d677ed3245c [diff] |
Do not try to read from the stdout/stderr streams of destroyed processes. According to https://bugs.openjdk.java.net/browse/JDK-4311711 , the behavior is undefined and it reproducibly results in hangs on Windows. This makes Ctrl-C on be able to interrupt Bazel during the execution phase, too. There are no guarantees about actually killing the child processes, though: Process.destroy() apparently leaves some child processes running. Unfortunately, Java doesn't offer a solution to this, so we'll have to resort to native code in some way. -- MOS_MIGRATED_REVID=125758911
{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.