| commit | f3e8cf0a2aa4a76dd59951a06670c6cc55a576a3 | [log] [tgz] |
|---|---|---|
| author | janakr <janakr@google.com> | Tue Oct 27 07:35:45 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Oct 27 07:36:59 2020 -0700 |
| tree | 8b47e04cab301dd50f62c9403048cd0d0daf0b03 | |
| parent | 22b4dbcaf05756d506de346728db3846da56b775 [diff] |
Make a failure to spawn the subprocess in a sandbox exit code 36 rather than 1. It's a local environmental error for the subprocess not to start, rather than a build failure, as evidenced by the other bits: Status.EXECUTION_FAILED is a "system" error and the suggestively named LOCAL_EXEC_ERROR. I would be happy to just migrate this code to EXECUTION_IO_EXCEPTION and change that exit code as well. This one seems more egregiously wrong, given that it has the "system" bits set in the SpawnResult, but that one also seems bad. RELNOTES: Bazel returns exit code 36 (rather than 1) if it fails to start a subprocess in a local sandbox due to environmental issues, for example, if the argument list is too long. PiperOrigin-RevId: 339245633
{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:
See CONTRIBUTING.md
