commit | 6ea8e256ff5799b9fcab7074c0cfa1e862fff34a | [log] [tgz] |
---|---|---|
author | adonovan <adonovan@google.com> | Mon Feb 03 14:33:14 2020 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Feb 03 14:34:07 2020 -0800 |
tree | c00e8e79c4cb84d46e964343a4f4f74f0fc62ea7 | |
parent | 90beb21a6d7324bbe97411db93d01b5d8785d00d [diff] |
bazel syntax: reduce log spam from tests ParserTest and ValidationTest no longer print their expected errors to the log. The root problem is in EventCollectionApparatus, which prints all errors, but it is so widely used that changing it is a bigger project. This change simply removes the two tests' dependency on the apparatus, which was overkill. Also: - make tests final to prevent subclassing, where possible. (If you make it private it silently fails to run.) - Simplify code to parse semantic options. PiperOrigin-RevId: 293006744
{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