| commit | 27aaccccb674090493d52d3340b7df69f5ed43f8 | [log] [tgz] |
|---|---|---|
| author | Fabian Meumertzheim <fabian@meumertzhe.im> | Tue Aug 15 15:20:57 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Aug 15 15:22:22 2023 -0700 |
| tree | 040ac102ae5c64dd7c99d7e5bc09df707f92b9d3 | |
| parent | 70fc57d29ce21204f28f8462627badbd5b750787 [diff] |
Include dependency edge info in transition errors When a Starlark transition implementation function fails, it now prints an error such as: ``` ERROR: /home/user/example/BUILD.bazel:3:11: On dependency edge //pkg:wrapper (ed19e2b) -|exports|-> //pkg:real_target: Errors encountered while applying Starlark transition ``` Previously, the generated error messages would only point to the BUILD file location of the target with the outgoing edge as well as a stack trace of the transition function (the latter only for Starlark errors, not those encountered during option conversion). Closes #19251. PiperOrigin-RevId: 557267979 Change-Id: I8988efde4ffb0ce0bc698640305b24e7b5f92cdd
{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
