| commit | 8c67e3e50f58780ed261289b1418e734a20bbb5a | [log] [tgz] |
|---|---|---|
| author | ulfjack <ulfjack@google.com> | Mon May 29 17:43:04 2017 +0200 |
| committer | László Csomor <laszlocsomor@google.com> | Tue May 30 09:56:29 2017 +0200 |
| tree | b38f87bd346d022f1f2728fa9923c6293b7d4af4 | |
| parent | 1cc7c0245770c120927f736c40fbe8988bb3c280 [diff] |
Remote worker: skip non-existent files after action execution Tests basically always finish with non-existent files, and this is not an error on the server side. Instead, the client (Bazel) checks whether all the files it expects are present. The test didn't catch this because it was silently falling back to local execution. Non-existent files were leading to an IOException, which caused the remote worker to log nothing, and silently return an error with no output. Log errors in the remote worker to make future debugging easier. Fixes #2887. PiperOrigin-RevId: 157400131
{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.