| commit | ff68b0a944ef2a3dcd639aac1ba682dfc1647ff5 | [log] [tgz] |
|---|---|---|
| author | Googler <jhorvitz@google.com> | Wed Jun 15 16:49:25 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jun 15 16:50:32 2022 -0700 |
| tree | 85d733e95a2b1c7a10e4c627b6b7cadad0223eb8 | |
| parent | 68f29c67098cedbfaa3ef011eef4df661860ac36 [diff] |
When rewinding actions that produce tree artifacts, invalidate the cached directory creation. Since the action is to be rewound, it will completely re-execute including `Action#prepare`, which deletes its outputs including tree directories. Invalidate these directories in the `knownDirectories` cache so that they are created again. This change only affects builds which use rewinding without an in-memory action filesystem. This will soon be integration tested as part of b/229395817 - in fact, that's how I encountered this bug. PiperOrigin-RevId: 455250588 Change-Id: I5ca188c95d4528d7fbbfcd108b0b2192f2321d8d
{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
