Avoid over-conservatively dirtying all aggregation artifact inputs (runfiles, filesets) during action rewinding. During action rewinding, we want to avoid dirtying all inputs to aggregator actions (like `RunfilesTree`, `FilesetTraversal`, `SymlinkTree`) unnecessarily. This change implements precise rewinding behind the `--experimental_precise_rewinding` flag: - In `ActionRewindStrategy`, when precise rewinding is enabled, aggregator actions only have their inputs that are in `lostInputsAndTransitiveOwners` dirtied and rewound. - Added `ActionExecutionMetadata#isAggregator` to identify the actions we care about. - Added `isAggregatorArtifact` check to make sure we don't skip nested/composed aggregator inputs (like intermediate Filesets) since we cannot easily verify if they contain lost inputs from the owners map alone. - Re-routed transitive `NestedSet` invalidation to use `addNestedSetPathsToRewindGraph` when precise is enabled. - Parameterized integration tests to verify correctness in both precise and imprecise modes. PiperOrigin-RevId: 948046090 Change-Id: Iddabeb6000d27d03656fc419c4745699c29cdb4f
{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.
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
