Fix bazel_toolchain_test This time for real. This rolls back bea9c01592a5, my previous attempt to fix the test. What happened: Before fdba19031961: The BUILD file was referencing the data as a directory, and the sandbox implementation was symlinking the entire directory (not individual files). As a result, the chmod call was succeeding, but *it was modifying the source tree*! After fdba19031961, before bea9c01592a5: The BUILD file was using a glob to enumerate individual files, and the individual symlinks in the sandbox are in a read-only file system. The chmod call was failing. After bea9c01592a5: Without the chmod call, the test passed because the files were still marked as executable *in the source tree* due to the pre-fdba19031961 code. However, it failed in a clean checkout. Solution: Reinstate the chmod call, but make sure all the files are copied into a temporary *empty* directory. Fixes #2891. PiperOrigin-RevId: 154436636
{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.