| commit | 376cd472bbf7d81c7feb79563e7894cc3d74151a | [log] [tgz] |
|---|---|---|
| author | Brentley Jones <github@brentleyjones.com> | Mon Mar 21 09:50:15 2022 -0500 |
| committer | GitHub <noreply@github.com> | Mon Mar 21 15:50:15 2022 +0100 |
| tree | 459221efbaf256c49b4e2e11a22f8679b2adee5c | |
| parent | 6d26dc74da2602817d56b0507ec79394c35a3781 [diff] |
Remote: Don't check TreeArtifact output (#15085) With a151116f7f671efea9a95f3e251561e53e535cca, we ignore action cache entry when checking the remote cache if a mandatory output of the Spawn is missing. However, this breaks Spawns that declare a directory output but don't generate anything under it. Since remote servers typically don't create directory ahead of time, and if the action itself doesn't create files under the directory, that directory will be eliminated from the action cache entry. This PR fixes that by not checking TreeArtifact output. Closes #15077. PiperOrigin-RevId: 436163970 (cherry picked from commit f5857830bb68bd05ffc257506575ed37a8128933) Co-authored-by: Chi Wang <chiwang@google.com>
{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
