Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
Used in:
Used in:
All numerical exit code associations correspond to pre-existing Bazel behavior. These associations are suspicious: - COMMAND_LINE_EXPANSION_FAILURE: this is associated with 2, the numerical exit code for "bad Bazel command line", but is generated when an action's command line fails to expand, which sounds similar but is completely different. - OUTPUT_FAILURE: this is associated with 6, an undocumented exit code. - INVALID_AQUERY_EXPRESSION: this is associate with 1, which is not documented for (a)query. TODO(b/138456686): Revise these after the (intentionally non-breaking) initial rollout of FailureDetail-based encoding.
Used in:
Used in:
Used in:
Deprecated: attempting to rewind a source artifact is now a hard crash.
Used in:
Used in:
TODO(b/138456686): this code should be deprecated in favor of more finely resolved loading-phase codes.
Failure modes described by this category pertain to the Bazel invocation configuration consumed by Bazel's analysis phase. This category is not intended as a grab-bag for all Bazel flag value constraint violations, which instead generally belong in the category for the subsystem whose flag values participate in the constraint.
Used in:
Used in:
This can come from either an invalid user-specified option or a configuration transition. There's no sure-fire way to distinguish the two possibilities in Bazel, so we go with the more straightforward command-line error exit code 2.
Failure modes specific to PROJECT.scl files.
Used in:
Additional data could include the build progress upload endpoint.
Used in:
Used in:
Additional data for partial failures might include the build report that failed to be written.
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
The name "COMMAND_UNKNOWN" might reasonably be interpreted as "command not found". The enum's default value should represent a lack of knowledge about the failure instead.
Used in:
Used in:
Used in:
Used in:
Indicates failure to correctly define a format function
Used in:
Used in:
Used in:
Used in:
Used in:
The cause chain of the crash, with the outermost throwable first. Limited to the outermost exception and at most 4 nested causes (so, max size of 5).
True when the root cause of the crash was not an OutOfMemoryError, but CRASH_OOM was chosen because an OutOfMemoryError was detected prior to the crash.
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
SOURCE_INPUT_MISSING
Used in:
All numerical exit code associations correspond to pre-existing Bazel behavior. These associations are suspicious: - REQUESTED_STRATEGY_INCOMPATIBLE_WITH_SANDBOXING (instead: 2?) - DEPRECATED_LOCAL_RESOURCES_USED (instead: 2?) TODO(b/138456686): Revise these after the (intentionally non-breaking) initial rollout of FailureDetail-based encoding.
Used in:
Used in:
Used in:
Used in:
Additional data could include external repository names.
Used in:
Used in:
Used in:
The FailureDetail message type is designed such that consumers can extract a basic classification of a FailureDetail message even if the consumer was built with a stale definition. This forward compatibility is implemented via conventions on FailureDetail and its submessage types, as follows. *** FailureDetail field numbers Field numbers 1 through 100 (inclusive) are reserved for generally applicable values. Any number of these fields may be set on a FailureDetail message. Field numbers 101 through 10,000 (inclusive) are reserved for use inside the "oneof" structure. Only one of these values should be set on a FailureDetail message. Additional fields numbers are unlikely to be needed, but, for extreme future- proofing purposes, field numbers 10,001 through 1,000,000 (inclusive; excluding protobuf's reserved range 19000 through 19999) are reserved for additional generally applicable values. *** FailureDetail's "oneof" submessages Each field in the "oneof" structure is a submessage corresponding to a category of failure. In each of these submessage types, field number 1 is an enum whose values correspond to a subcategory of the failure. Generally, the enum's constant which maps to 0 should be interpreted as "unspecified", though this is not required. *** Recommended forward compatibility strategy The recommended forward compatibility strategy is to reduce a FailureDetail message to a pair of integers. The first integer corresponds to the field number of the submessage set inside FailureDetail's "oneof", which corresponds with the failure's category. The second integer corresponds to the value of the enum at field number 1 within that submessage, which corresponds with the failure's subcategory. WARNING: This functionality is experimental and should not be relied on at this time. TODO(mschaller): remove experimental warning
Used in:
, ,A short human-readable message describing the failure, for debugging. This value is *not* intended to be used algorithmically.
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
TODO(b/166268889): this code should be deprecated in favor of more finely resolved loading-phase codes.
Used in:
The distinction between a failure to write a single info item and a failure to write them all seems sketchy. Why do they have different exit codes? This reflects current Bazel behavior, but deserves more thought.
Used in:
Used in:
Used in:
Unknown interrupt. Avoid using this code, instead use INTERRUPTED.
Command was interrupted (cancelled).
The following more specific interrupt codes have been deprecated and consolidated into INTERRUPTED.
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Deprecated: validation is now implemented by the option converter.
Deprecated: no tenured collectors found is now a crash on startup.
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
,Failure while evaluating or applying @_builtins injection. Since the builtins .bzl files are always packaged with Blaze in production, a failure here generally indicates a bug in Blaze.
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Deprecated - folded into SYNTAX_ERROR.
Deprecated - folded into SYNTAX_ERROR.
Deprecated - folded into SYNTAX_ERROR.
Deprecated - folded into SYNTAX_ERROR.
Deprecated - folded into SYNTAX_ERROR.
Indicates the user specified invalid query syntax.
Indicates any usage of flags that must not be combined.
Indicates a non-detailed exception that halted a query. This is a deficiency in Blaze/Bazel and code should be changed to attach a detailed exit code to this failure mode.
Failure details for errors produced during remote analysis caching.
Used in:
Used in:
Used in:
The association of some of these options with exit code 2, "command line error", seems sketchy. Especially worth reconsidering are the channel init failure modes, which can correspond to failures occurring in gRPC setup. These all correspond with current Bazel behavior.
Used in:
Used in:
Used in:
Credentials could not be read from the requested file/socket/process/etc.
Credentials could not be written to a shared, temporary file.
Used in:
Used in:
Used in:
Used in:
Failure details for errors produced when using Skyfocus
Used in:
Used in:
The defined working set cannot be used for the focused targets. For example, this happens when the intersection of the working set and the transitive closure of the focused target is empty.
The user needs to augment their working set to include the new file(s).
Used in:
For Codes describing generic failure to spawn (eg. EXECUTION_FAILED and EXECUTION_DENIED) the `catastrophic` field may be set to true indicating a failure that immediately terminated the entire build tool.
If Code is NON_ZERO_EXIT, the `spawn_exit_code` field may be set to the non-zero exit code returned by the spawned process to the OS. NOTE: This field must not be confused with the build tool's overall exit code.
Used in:
See the SpawnResult.Status Java enum for definitions of the following Spawn failure codes.
Note: Spawn OUT_OF_MEMORY leads to a BUILD_FAILURE exit_code because the build tool itself did not run out of memory.
TODO(b/138456686): this code should be deprecated when SpawnResult is refactored to prohibit undetailed failures
This also includes other remote cache errors, not just evictions, if --incompatible_remote_use_new_exit_code_for_lost_inputs is set. TODO: Rename it to a more general name when --experimental_remote_cache_eviction_retries is moved to non-experimental.
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
The class name of the java.lang.Throwable.
The throwable's message.
The result of calling toString on the deepest (i.e. closest to the throwable's construction site) 1000 (or fewer) StackTraceElements. Unstructured to simplify string matching.
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
,Used in:
Used in:
Failure details about Bazel's WORKSPACE features.
Used in:
Used in:
See `managed_directories` in https://bazel.build/rules/lib/globals#workspace.