| commit | 7cf90f91c7a89e605ade6df010cae51ca58d91b8 | [log] [tgz] |
|---|---|---|
| author | Googler <jhorvitz@google.com> | Thu Jun 09 12:55:51 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jun 09 12:57:07 2022 -0700 |
| tree | 706ec272e2af6a594f6f4cfb556662151dff6be4 | |
| parent | 1aca439d10011fb3ce23e7ba1766a821b6a3f5c2 [diff] |
Automated rollback of commit 442155f19f2c2764839327c8be3d3ab70edf1910. *** Reason for rollback *** Rolling forward with fix for b/235458248: consider it a "stale read" if a node was created for rewinding while a fetch was pending. Unfortunately an integration test is not feasible because we don't have enough synchronization hooks - we would need to start a fetch, then delay it until after rewinding is initiated and calls `createIfAbsentBatch`. Even then, we would still need to simulate another dependency branch first seeing the rewinding-created node (not done) then later seeing the remote node (done), causing a crash because it's unexpectedly done. Instead, I've added a unit test to `StaleReadRejectingGraphInjectorTest`. *** Original change description *** Automated rollback of commit a0a0d09debd090fbe74bba59b5d6d3107aaf97e9. *** Reason for rollback *** b/235458248 *** Original change description *** Create a dedicated graph lookup reason for rewinding and add a wildcard to `createIfAbsentBatch` to match `getBatch`. PiperOrigin-RevId: 453991978 Change-Id: Id35366674fb30ca5c7ac2272a5c9f7334f7ba901
{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
