| commit | 0529fdb18f42c1381cdefe7534e5b5d86ac1e673 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Tue Jun 07 00:38:03 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jun 07 00:39:30 2022 -0700 |
| tree | d1ad893703bb45a619078c2d8d621ae96c87a166 | |
| parent | 7de4fab0d8b507f3790533e1ae18e94dca916d04 [diff] |
Prep build output tests for sh_library as a Starlark rule When sh_library is implemented as a Starlark rule, the traceback includes the location of the sh_library implementation. Because this would make the test fragile, this CL adjusts tests in two different ways: 1) checking only the portion of the traceback for the pieces defined in the test. 2) implementing the test using filegroup instead of sh_library. TESTED: Ran these tests with and without a patch to exports.bzl that enables the sh_library as a Starlark rule by default. PiperOrigin-RevId: 453370399 Change-Id: Ic3ad637e170186abc4c27d2b8682d3dbaa738aff
{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
