| commit | 4001dddc38b07fe0ee86f6a9e95ff4a92276bb2d | [log] [tgz] |
|---|---|---|
| author | elenairina <elenairina@google.com> | Fri Jun 08 01:42:20 2018 -0700 |
| committer | Copybara-Service <copybara-piper@google.com> | Fri Jun 08 01:43:29 2018 -0700 |
| tree | d60af84b2654414ccd80b7df1a4561e046cbc9fa | |
| parent | 5df8eb24f84a6943e70876c805c77f06e719dcd7 [diff] |
Make JavaBuilder use a unique coverage metadata directory for each test instead of the same directory for all the tests. The previous implementation was using one directory for instrumenting the classes of a jar. For each each jar the metadata directory was deleted if it already existed. This is problematic for local execution when multiple tests are run in parallel because some threads will try to delete the directory and some will try to perform read/write operations on it. This is an important fix for Bazel coverage users. Fixes #4398. RELNOTES: Java coverage works now with multiple jobs. PiperOrigin-RevId: 199764483
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds 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:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.