| commit | 76ff8561eeadbaf6c70a229362e679b49467a5d1 | [log] [tgz] |
|---|---|---|
| author | Googler <chiwang@google.com> | Fri Jul 21 05:41:05 2023 -0700 |
| committer | fweikert <fwe@google.com> | Thu Jul 27 21:57:05 2023 +0200 |
| tree | 5414c7350d2068b1198ae719c50e1edabec3016d | |
| parent | 5d62b252ad9906986bc3035412653c9d07e5f2dc [diff] |
Correctly handle symlinks when prefetching. In https://github.com/bazelbuild/bazel/commit/5c4cf47a131c84506aad9ce0e014c6643c31a4ac, we replaced `path = path.getRelative(path.readSymbolicLink())` with `path = path.resolveSymbolicLink`. While the former one is wrong for relative symlinks, it actually works for absolute symlinks. The latter one, however, doesn't work if the target doesn't exist on local file system -- and this is the case for most of builds using our internal version of BwoB. This CL fixes that issue by correctly handle both absolute and relative symlinks. Additionally, it correctly handles the case where a symlink points to a tree output. Moved symlink integration tests to the base test class. PiperOrigin-RevId: 549921885 Change-Id: If4009525499f4d0625e7725faf4bb0675984c299
{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
