| commit | 672cb580c2480c7c172fadfd4c5151bae5775245 | [log] [tgz] |
|---|---|---|
| author | Julio Merino <jmmv@google.com> | Thu Sep 01 16:39:17 2016 +0000 |
| committer | Klaus Aehlig <aehlig@google.com> | Fri Sep 02 08:24:37 2016 +0000 |
| tree | d13dfab6568f2aac42e0ac31ef774f7a8f527057 | |
| parent | 26389edbc1595599de67742effd13ca7da829c05 [diff] |
Fix tests by explicitly passing TEST_TMPDIR to mk*temp. We need to tell mktemp to explicitly create temporary files and directories under TEST_TMPDIR. The default of picking up the TMPDIR value (which may be unset) or /tmp may not work and was causing two tests to fail. I suspect that paths outside of TEST_TMPDIR may not be writable due to our sandboxing features. -- MOS_MIGRATED_REVID=131957733
{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.