| commit | dca18400dd00da500accd447d1d3cfc248956478 | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Thu Jun 09 08:46:29 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Thu Jun 09 11:27:06 2016 +0000 |
| tree | f7b7331b8c31723298a8638ca5f5cba7d9dc2484 | |
| parent | b5692bde922c042066a979f9275657648e16d79d [diff] |
experimental ui: not only report errors, but also failures immediately When a user is running a test with lots of runs (e.g., to debug flakyness), it is useful to immediately see individual failures and not wait for the summary of tests. Therefore, report failure events just like errors in the scrollback buffer. -- Change-Id: If32d1201f59cec75d99d18a50fc881c3596c3081 Reviewed-on: https://bazel-review.googlesource.com/#/c/3770 MOS_MIGRATED_REVID=124437705
{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.