| commit | da4f6d10ec39d0780c71ed84dae0a03193851246 | [log] [tgz] |
|---|---|---|
| author | pcloudy <pcloudy@google.com> | Thu Feb 10 07:03:17 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Feb 10 07:04:47 2022 -0800 |
| tree | a221b5d531f5eda1a548d4b93100d240cae8552e | |
| parent | b6024258c5b9b396b022bad6e7e3d64423048289 [diff] |
Make `TEST_REPOSITORY_HOME` stable for macOS and Windows We used to pass `--test_env=TEST_REPOSITORY_HOME=$OUTPUT_BASE/external` for running tests, but the $OUTPUT_BASE is calculated based on the current working directory. For Linux, the working directory is stable as we run tests inside docker. For macOS and Windows, the working directory contains the machine name, which caused TEST_REPOSITORY_HOME to be different from one presubmit to another and led to low cache hit rate on those two platforms. This PR fixes the issue by creating a symlink to $OUTPUT_BASE/external, and always pass the same path to TEST_REPOSITORY_HOME RELNOTES: None PiperOrigin-RevId: 427738284
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
