Include configuration mnemonic in action execution error messages When an action execution fails, `CommandFailureUtils.describeCommandFailure` previously formatted the error without the configuration mnemonic/checksum: Before: ``` ERROR: /path/to/pkg/BUILD:1:1: CppCompile hello_binary.o failed: (Exit 1): gcc failed: error executing CppCompile command (from target //:hello_binary) /usr/bin/gcc ... ``` If `//:hello_binary` failed when built under a configuration transition (e.g. as a dependency of `//:broken_hello_filegroup`), users could not see from the error output why the action failed in that context but succeeded when built directly. After: ``` ERROR: /path/to/pkg/BUILD:1:1: CppCompile hello_binary.o failed: (Exit 1): gcc failed: error executing CppCompile command (from target //:hello_binary [k8-fastbuild-ST-4e2b1c0a]) /usr/bin/gcc ... ``` This CL includes the configuration checksum / mnemonic in action execution error messages, making transition-specific failures immediately identifiable. Fixes part of https://github.com/bazelbuild/bazel/issues/18139. PiperOrigin-RevId: 970402874 Change-Id: Iba3dab59f3e0a2229f5e1ccea5db9589727d05c7
{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.
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
