Relocate the sandbox debug suggestion to the build summary. When a sandboxed action failed, AbstractSandboxSpawnRunner directly emitted an Event.info with the --sandbox_debug suggestion. This caused the hint to appear mid-execution right before the compiler's stderr output, interleaving Bazel advice into the compiler error. Remove the direct reporter call from AbstractSandboxSpawnRunner and instead print the --sandbox_debug suggestion in BuildResultPrinter at the end of the build alongside --verbose_failures. Before: ``` ERROR: /path/to/BUILD:15:11: GoCompilePkg //pkg:go failed: (Exit 1): builder failed: ... Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging pkg/auth.go:6:2: result declared but not used Target //pkg:go failed to build Use --verbose_failures to see the command lines of failed build steps. ``` After: ``` ERROR: /path/to/BUILD:15:11: GoCompilePkg //pkg:go failed: (Exit 1): builder failed: ... pkg/auth.go:6:2: result declared but not used Target //pkg:go failed to build Use --verbose_failures to see the command lines of failed build steps. Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging ``` Part of https://github.com/bazelbuild/bazel/issues/15820 RELNOTES: None. PiperOrigin-RevId: 972632303 Change-Id: I2ee2517c9262eb3af48d7b27b3621702b8e5c0bc
{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
