| commit | 218c36341b2911002164c6ccac9decf4fed9e380 | [log] [tgz] |
|---|---|---|
| author | Benjamin Peterson <bp@benjamin.pe> | Wed Jun 28 14:24:03 2017 +0200 |
| committer | Marcel Hlopko <hlopko@google.com> | Wed Jun 28 15:27:29 2017 +0200 |
| tree | efa93bb1a2788e3884f0be821084828636bcb311 | |
| parent | 224a0da597ddae822a0a9b2ae314a25fa6481bfe [diff] |
Ensure shards of the same test have unique names in the fallback xml test-setup.sh currently uses the test target name as the "name" attribute in the xml output's "testcase" element. This ensures names in the xml are unique across the workspace for unsharded tests. However, sharded tests all end up with the same "name" attribute. This angers some junitxml processing tools, which can be quite persnickity about uniqueness. Let's generate unique test names of the form "mytest_shard_N/M" for sharded tests. Change-Id: I6ea82f56846b88449da977dc6629a73b695a485e PiperOrigin-RevId: 160397341
{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.