commit | 97966cc294fcaa34e0eef1aa971e324c91314389 | [log] [tgz] |
---|---|---|
author | elenairina <elenairina@google.com> | Wed Jul 19 15:40:11 2017 +0200 |
committer | Klaus Aehlig <aehlig@google.com> | Wed Jul 19 16:53:26 2017 +0200 |
tree | 6fcf3862cb9357908ad21cd0d2a360acd8ac2be3 | |
parent | f1843dfc4ebc4c8c54b677db84d3e3407897efef [diff] |
Update jacoco coverage runner to consider some edge cases. After running the new coverage implementation on some real targets I found the following. 1. Inner classes with the same name could be added from different jars. Addressed this by analyzing classes with the same name exactly once. 2. Auto-generated files were added to the coverage report. This is resolved first on the blaze/bazel side by adding to the files with the exec paths of the instrumented files only those that are source files and on the coverage runner side by discarding all the files that are not in that file. PiperOrigin-RevId: 162478894
{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 system. 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.