| commit | e1ab2ba5216bec05ee8cb08ba469b97c1f88a577 | [log] [tgz] |
|---|---|---|
| author | Brian Silverman <bsilver16384@gmail.com> | Tue Apr 26 12:15:25 2016 +0000 |
| committer | Yun Peng <pcloudy@google.com> | Tue Apr 26 14:39:38 2016 +0000 |
| tree | a35bce5aaad70a120a5818f7c879b722e0d26d35 | |
| parent | d9da60f49d367e935307f71b8f1aa2c03b7aa20b [diff] |
Print out the error from getpwuid instead of segfaulting In a mailing list discussion [1], somebody reported namespace-sandbox segfaulting, which was traced down to something with getpwuid. This debugging would be a lot easier if bazel printed out the error instead of segfaulting. [1] https://groups.google.com/d/topic/bazel-discuss/FR949mCW9cA/discussion -- Change-Id: I96320287b1886347343c1a50d660c097534d91d2 Reviewed-on: https://bazel-review.googlesource.com/#/c/3400 MOS_MIGRATED_REVID=120803905
{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.