| commit | 32714ee3dba86f31a8202023ba94d2f7c60ee828 | [log] [tgz] |
|---|---|---|
| author | trybka <trybka@google.com> | Wed Apr 13 08:56:48 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 13 08:58:13 2022 -0700 |
| tree | d53f37585afa91497866c4a8fdaab57014392aa8 | |
| parent | 90fe1b2bb2604e2acb3db56f18a4532967aa1f89 [diff] |
## Starlark `cc_test` fixes. * Restructure `cc_test` to use a toolchain alias. This will allow `cc_test` to work in Bazel (and tests) without a "dummy" toolchain needing to be registered. This makes `cc_test` use the legacy flow when toolchains are not registered--requiring an additional flag if they are. This is a temporary measure to permit switching off `native.cc_test` before [Optional Toolchains](https://github.com/bazelbuild/bazel/issues/14726) lands. * Add coverage-related tools (e.g. collect_cc_coverage.sh) necessary for Bazel to collect coverage from cc_test(s) PiperOrigin-RevId: 441494074
{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:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
