| commit | e9022f6731b4f62d3a08bdc4eacce70ad28e3c78 | [log] [tgz] |
|---|---|---|
| author | Googler <plf@google.com> | Mon Feb 19 02:39:27 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Feb 19 02:41:29 2024 -0800 |
| tree | 1009db8563b3ac2fd8d3d7febc85e6a55da8fbe9 | |
| parent | 541aa3b4d384b07f6e0242c390802f965d7d2839 [diff] |
Reuse runfiles in tests with --reuse_sandbox_directories Test actions are guaranteed to have a runfiles directory with the test name as part of the name. The path to the directory is unique between tests. If two tests (foo and bar) have the directory <source-root>/pkg/my_runfiles as part of their runfiles and this directory contains 1000 files, we would be symlinking the 1000 files for each test since the paths do not coincide. To make sure we can reuse the runfiles directory we must rename the old runfiles directory for the action that was stashed to the path that is expected by the current test. PiperOrigin-RevId: 608273594 Change-Id: Iea46fa3600d29d9a5747c93f104c0a5b23d1ea53
{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
