| commit | e411fa74176cdc54f84d62c189d042e9fb6d5c79 | [log] [tgz] |
|---|---|---|
| author | ulfjack <ulfjack@google.com> | Tue Jan 28 08:40:19 2020 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 28 08:41:14 2020 -0800 |
| tree | 0c2e0944f741cc5026611db45e34d4acb30c9578 | |
| parent | e8d482496f705304d21c938ec44dc578997ae942 [diff] |
Add a flag to declare coverage dir as tree artifact This adds an experimental flag that changes the behavior of tests when run with coverage such that the _coverage directory is declared as a tree artifact. This makes it significantly easier to debug coverage runs when sandboxing (the default) or remote execution are enabled. Without this, the files are implicitly ignored, and only the coverage.dat file is brought back into the output tree. If for some reason the additional steps to generate the coverage.dat file fail, then that the file is empty or non-existent. This also provides a workaround for languages that cannot currently generate lcov format coverage data. By bringing back the individual files, the user can use a post-process to merge the data. It's not perfect, but it's simple and effective. I used it myself to debug a coverage issue due to incorrect file paths w/ gcc on MacOS. Unfortunately, the coverage collector script generates a number of temporary files in the _coverage directory which we generally do not want (or need) to bring back into the output tree. This will have to be addressed separately. PiperOrigin-RevId: 291940271
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only 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
