commit | 2a61fe711e297773d0df24b2dfe5ad83d1a24071 | [log] [tgz] |
---|---|---|
author | Googler <leba@google.com> | Tue May 07 01:26:49 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Tue May 07 01:29:03 2024 -0700 |
tree | 6afa76520c149a3830c6eb91b86046b55405feb3 | |
parent | 5afbe2397476e3f4c4d2adfda6809a316a8de7c2 [diff] |
Incorporate skymeld inconsistencies into the rewinding/node dropping receivers. Current state: blaze in skymeld + rewinding just uses the `RewindableGraphInconsistencyReceiver`, which doesn't take into account skymeld inconsistencies and is mutually exclusive with `SkymeldInconsistencyReceiver`. After this CL: `RewindableGraphInconsistencyReceiver` and `NodeDroppingInconsistencyReceiver` handles skymeld-specific inconsistencies as well. Code changes: - `SkymeldInconsistencyReceiver` is removed and its content is distributed to the rewinding/node dropping inconsistency receivers. Behavior changes: - `RewindableGraphInconsistencyReceiver` and `NodeDroppingInconsistencyReceiver` handles skymeld-specific inconsistencies as well. - Unexpected skymeld inconsistencies will throw, instead of sending a BugReport like before. --- Since https://github.com/bazelbuild/bazel/commit/5b52f018b193be02fd11de9bc89c9f9d49bf5b3f, rewinding is already compatible with Skymeld. PiperOrigin-RevId: 631332866 Change-Id: I3d222c23d5e40aa7a86546039bfb795f7b812c2c
{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