Automated rollback of commit bcbd956399c8322ede781ee5e2514de6171ca962. *** Reason for rollback *** https://github.com/bazelbuild/bazel/commit/4d6513b54fa07321115cac350553b29914d43a65 was innocent. The issue was caused by a synchronization issue: even though BuildEventStreamer expects no events to be posted after BuildCompleteEvent, there is no guarantee that the UI thread does not do so and if it does, it breaks the logic that sets last_message. This happens because progress events in response to console messages announce the next progress event in turn and last_message is set when there are no more announced but not posted events. Thus, any console write after BuildCompleteEvent but before the last event announced before BuildCompleteEvent is posted results in an event that is announced but never posted. *** Original change description *** Rollback of https://github.com/bazelbuild/bazel/commit/4d6513b54fa07321115cac350553b29914d43a65 due to user breakage reports. PiperOrigin-RevId: 636821481 Change-Id: I9c2f8a51889fc03c054233beb31873d1dc63fd08
{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
