| commit | 95e948457994ce0e6381da0b1d734be1aec8f63b | [log] [tgz] |
|---|---|---|
| author | bazel.build machine account <ci.bazel@gmail.com> | Tue Nov 11 09:53:12 2025 +0100 |
| committer | GitHub <noreply@github.com> | Tue Nov 11 08:53:12 2025 +0000 |
| tree | 765abc85641f16c154ea283f9dfce92c7290da01 | |
| parent | 3873b4c7493566cb72fc4e94c37922b42ecc0f72 [diff] |
[9.0.0] Remove the assertion which disallows stopBranch to be called twice. (#27620) Back in the time when this assertion was introduced in 4b1cdfc6df3d662dbc489d21e0ee8d69515e7ee1, it was expected that `stopBranch` should not be called more than once. However, in the current state, the `stopBranch` function can be called twice when a remote branch wins the race in a dynamic execution, but falls back to a local execution due to issues like downloading error. In that case, the fallback local execution can call `stopBranch` for the second time. We believe this is a valid case and we should remove this assertion to address the issue. Fixes #27422. PiperOrigin-RevId: 830370258 Change-Id: Ia8271d8bff66d60596b43d3e908a30ac9e8a5d25 Commit https://github.com/bazelbuild/bazel/commit/3c04b654e816d2cb3e8fe4794e35fbafb2ac5d32 Co-authored-by: bangbang <bangbang@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
