| commit | 2a8c634001f3c145ed4fd11915d8f661ebf07b37 | [log] [tgz] |
|---|---|---|
| author | bazel.build machine account <15028808+bazel-io@users.noreply.github.com> | Wed Dec 06 13:22:43 2023 +0100 |
| committer | GitHub <noreply@github.com> | Wed Dec 06 13:22:43 2023 +0100 |
| tree | 52c42b0f963a9892e6f3e58f804c51feb32d9a1f | |
| parent | d2dbad3fbb55fd1a932298ea5b6b5660b6084a4c [diff] |
[7.0.0] Add more details to the warning message in --keep_going mode (#20450)
The current message is too generic and not helpful for the user.
```
Before:
WARNING: errors encountered while analyzing target '//:bin': it will not be built
---
After:
WARNING: errors encountered while analyzing target '//:bin', it will not be built.
Target //:bin is incompatible and cannot be built, but was explicitly requested.
Dependency chain:
//:bin (8250b5) <-- target platform (@@local_config_platform//:host) didn't satisfy constraint @@platforms//:incompatible
```
Fixes https://github.com/bazelbuild/bazel/issues/20443
Commit
https://github.com/bazelbuild/bazel/commit/c5493b9557502fe6ec48e78b0b5f06f4c1d75238
PiperOrigin-RevId: 588363260
Change-Id: I70e151cd9baa6a0dd7b307b7ddeb9f43ee30b526
Co-authored-by: Googler <leba@google.com>{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
