Only mark a node changed if it has not been scheduled for evaluation. https://github.com/bazelbuild/bazel/commit/900a965335ae268807dc4de26afb42de4c79c8aa introduced a method for atomically marking a node changed if it is in the `CHECK_DEPENDENCIES` state. This is insufficient to determine whether marking the node changed is safe: it may be in `CHECK_DEPENDENCIES` even if dependency checking has commenced. The method is renamed to `tryPromoteDirtyToChanged` and additionally checks that the node has not been scheduled for evaluation. PiperOrigin-RevId: 1020567075 Change-Id: I293e6fd1fd42d1f863a7a10d6876bfce381dd631
{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
