Miscellaneous fixes to tests to avoid using --test_arg as no-op, etc. Instead of using --test_arg as a no-op configuration setting, use a garbage cpu value (since not building anyway), define and define_values, or just change the associated targets to test targets (to avoid any trimming for when --trim_test_configuration is on). These are not BuildViewTestCase so introducing the DummyTestFragment is non-trivial hence the use of 'different' 'no-op' configuration flags. PiperOrigin-RevId: 366139254
{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
