| commit | 64f80799ed5c6369ffb6814f939a7964b0fa7c49 | [log] [tgz] |
|---|---|---|
| author | laszlocsomor <laszlocsomor@google.com> | Tue Apr 04 12:00:45 2017 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Tue Apr 04 18:38:04 2017 +0200 |
| tree | 4e181bf43ed42af8ae2d73e184e8c6ae7268dc59 | |
| parent | 19e9e90e62d4ef1304bb23dfe74ad1155e571505 [diff] |
Windows, JNI: non-zero exit code for termination Terminate processes and job objects with non-zero exit code. Zero was the most unfortunate exit code possible because it made the Java side believe that the process exited successfully. There's another bug in the Java side too where StandaloneSpawnStrategy ignores the thread's interruption state. I'll fix that in a separate change. Fixes https://github.com/bazelbuild/bazel/issues/2774 Change-Id: I01b3d95848cb04618395c9ef2fa0d1a406b25cca PiperOrigin-RevId: 152119343
{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.