| commit | 7a230fddd4db33bccc0ae99f46a91b48a668edbb | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Fri Jun 17 14:19:32 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jun 17 14:20:50 2022 -0700 |
| tree | 966d18a5bf96ca93c2b9195ce15cc99bbb705023 | |
| parent | 8b5ed8aac2b25180fbfac0ff27ebe3998a61209a [diff] |
Make Bazel tests compatible with Starlark implementation of Python rules Summary of changes: * Remove usage of Python rules where not necessary; the Python rules were/are being used to test features that aren't specific to the Python rules. * Use regex matching for failures instead of exact strings. The Starlark rules have slightly different phrasing or orderings of elements that don't affect behavior. This also makes the tests less brittle overall. * Disable attempting to use the Starlark implementation in all the tests requiring Python 2 (e.g. srcs_version checking etc). The Starlark implementation doesn't currently (and probably never will) support Python 2. https://github.com/bazelbuild/bazel/issues/15684 filed to track removal of it in Bazel. * Disable attempting to use the Starlark implementation where toolchain resolution is required. This will eventually be implemented, but isn't is use at Google and otherwise blocks switching internally. * Tests verifying warnings are printed were removed; Starlark doesn't provide a warning facility. * Stamping is disabled in various tests because, with the Starlark implementation, it requires remote execution of actions, which some tests aren't setup for (they never needed it previously). Rather than set this up, stamping was disabled (affected tests don't require stamping anyways). PiperOrigin-RevId: 455695015 Change-Id: I82822eff05b6c0a66e65f131c9e1c8784b1573ac
{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
