| commit | f6cc8ac7f5673cb72bb55346689ded9156356a0e | [log] [tgz] |
|---|---|---|
| author | michajlo <michajlo@google.com> | Mon Jun 07 12:04:04 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jun 07 12:05:13 2021 -0700 |
| tree | e4518cff5c497f0232c57116b7bdcee50caad704 | |
| parent | 13d1b2afb15519636d34eb1cdb38bf4457d6c201 [diff] |
Delete defunct test suite infrastructure Everything but supportedOs is never read in practice. They were probably used at some point, but we've migrated much of the test suite infrastructure over to regular old BUILD-defined tests. Deleted the attributes that were easy, but left size since it'll be a larger effort to clean up all of its vestigial uses. `tolerateEmptyTestSuites` is no longer used. In fact it was actually harmful since it gave the impression that it actually worked - `TautologyTest` would get picked up by the classpath-scanning test search of c.g.devtools.build.lib, which every use of the test suite builder would use, so test suites were never really empty in practice and would blindly succeed due to `TautologyTest` blindly succeeding. Alternatively we _could_ go the other direction and leave things as they are with the eventual goal of improving the test-suite infra. However, we've already moved quite a bit away from the point where it'd make sense to do that, which is why it was so easy do delete all of this functionality. Also, as noted in the previous paragraph, the framework actually hides bugs, so removing it reduces room for error. PiperOrigin-RevId: 377972815
{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
