| commit | 4c3d925e286318c4c94d4c28e1062825455c5933 | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Tue Feb 28 15:21:41 2017 +0000 |
| committer | Yue Gan <yueg@google.com> | Tue Feb 28 17:02:12 2017 +0000 |
| tree | 1ceafe3f3c8a51f9176f257fef24771f5a86dd46 | |
| parent | 691fbc1a5fd3ab03ab6c21e6c04fa9c528bbf1ba [diff] |
In SkyFunctionEnvironment post progress-like events immediately In Skyframe Evaluation, events reporting about progress are meant to be seen immediately by the environment. More over, they are not to be replayed when taking this SkyFunction out of cache. So change the custom implementation of the StoredEventHandler in the SkyFunctionEnvironment to forward appropriately. -- Change-Id: I30baf0088595ef684f16270f11668e980e65aa41 Reviewed-on: https://cr.bazel.build/9112 PiperOrigin-RevId: 148766400 MOS_MIGRATED_REVID=148766400
{Fast, Correct} - Choose two
Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google‘s software, and thus it has been designed to handle build problems present in Google’s development environment, including:
A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.
An emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.
Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.
Find more background about Bazel in our FAQ.