| commit | 9a4dffe435385dff9e9095be6c24834bd1d193da | [log] [tgz] |
|---|---|---|
| author | László Csomor <laszlocsomor@google.com> | Mon Dec 12 09:59:38 2016 +0000 |
| committer | John Cater <jcater@google.com> | Mon Dec 12 20:35:19 2016 +0000 |
| tree | 0f1afce784d57f6d9a6ca2d53a7c90825a0b7e3d | |
| parent | 68e850ff8df0e381bd224d9926b400b7320d4fb8 [diff] |
Ijar: remove spurious error message Commit 645dbc4 moved the file stating logic to platform_utils.cc into the `stat_file` method, then commit 8d6da00 added error reporting to that method so callers wouldn't need to report errors on their own. Problem is, one of the callers was using stat_file for simple file existence checking so reporting an error there was spurious. Fixes https://github.com/bazelbuild/bazel/issues/2201 -- Change-Id: I40d1ee2bad8f3d03627c0b5c0bfd593bb5289d23 Reviewed-on: https://cr.bazel.build/7810 PiperOrigin-RevId: 141739581 MOS_MIGRATED_REVID=141739581
{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.