package failure_details

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message ActionCache

failure_details.proto:711

Used in: FailureDetail

enum ActionCache.Code

failure_details.proto:712

Used in: ActionCache

message ActionQuery

failure_details.proto:794

Used in: FailureDetail

enum ActionQuery.Code

failure_details.proto:806

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: ActionQuery

message ActionRewinding

failure_details.proto:1027

Used in: FailureDetail

enum ActionRewinding.Code

failure_details.proto:1028

Used in: ActionRewinding

message Analysis

failure_details.proto:1173

Used in: FailureDetail

enum Analysis.Code

failure_details.proto:1174

Used in: Analysis

message BuildConfiguration

failure_details.proto:590

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: FailureDetail

enum BuildConfiguration.Code

failure_details.proto:591

Used in: BuildConfiguration

message BuildProgress

failure_details.proto:257

Used in: FailureDetail

enum BuildProgress.Code

failure_details.proto:258

Used in: BuildProgress

message BuildReport

failure_details.proto:351

Used in: FailureDetail

enum BuildReport.Code

failure_details.proto:352

Used in: BuildReport

message CanonicalizeFlags

failure_details.proto:576

Used in: FailureDetail

enum CanonicalizeFlags.Code

failure_details.proto:577

Used in: CanonicalizeFlags

message CleanCommand

failure_details.proto:857

Used in: FailureDetail

enum CleanCommand.Code

failure_details.proto:858

Used in: CleanCommand

message ClientEnvironment

failure_details.proto:302

Used in: FailureDetail

enum ClientEnvironment.Code

failure_details.proto:303

Used in: ClientEnvironment

message Command

failure_details.proto:535

Used in: FailureDetail

enum Command.Code

failure_details.proto:536

Used in: Command

message ConfigCommand

failure_details.proto:875

Used in: FailureDetail

enum ConfigCommand.Code

failure_details.proto:876

Used in: ConfigCommand

message ConfigurableQuery

failure_details.proto:885

Used in: FailureDetail

enum ConfigurableQuery.Code

failure_details.proto:886

Used in: ConfigurableQuery

message CppCompile

failure_details.proto:1037

Used in: FailureDetail

enum CppCompile.Code

failure_details.proto:1038

Used in: CppCompile

failure_details.proto:1118

Used in: FailureDetail

enum CppLink.Code

failure_details.proto:1119

Used in: CppLink

message Crash

failure_details.proto:311

Used in: FailureDetail

enum Crash.Code

failure_details.proto:312

Used in: Crash

message CrashOptions

failure_details.proto:483

Used in: FailureDetail

enum CrashOptions.Code

failure_details.proto:484

Used in: CrashOptions

message DiffAwareness

failure_details.proto:1295

Used in: FailureDetail

enum DiffAwareness.Code

failure_details.proto:1296

Used in: DiffAwareness

message DumpCommand

failure_details.proto:906

Used in: FailureDetail

enum DumpCommand.Code

failure_details.proto:907

Used in: DumpCommand

message DynamicExecution

failure_details.proto:1076

Used in: FailureDetail

enum DynamicExecution.Code

failure_details.proto:1077

Used in: DynamicExecution

message Execution

failure_details.proto:407

Used in: FailureDetail

enum Execution.Code

failure_details.proto:408

Used in: Execution

message ExecutionOptions

failure_details.proto:509

Used in: FailureDetail

enum ExecutionOptions.Code

failure_details.proto:516

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: ExecutionOptions

message ExternalDeps

failure_details.proto:1282

Used in: FailureDetail

enum ExternalDeps.Code

failure_details.proto:1283

Used in: ExternalDeps

message ExternalRepository

failure_details.proto:246

Used in: FailureDetail

enum ExternalRepository.Code

failure_details.proto:247

Used in: ExternalRepository

message FailAction

failure_details.proto:1088

Used in: FailureDetail

enum FailAction.Code

failure_details.proto:1089

Used in: FailAction

message FailureDetail

failure_details.proto:80

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: build_event_stream.ActionExecuted, build_event_stream.TargetComplete

message FailureDetailMetadata

failure_details.proto:28

message FetchCommand

failure_details.proto:720

Used in: FailureDetail

enum FetchCommand.Code

failure_details.proto:721

Used in: FetchCommand

message Filesystem

failure_details.proto:492

Used in: FailureDetail

enum Filesystem.Code

failure_details.proto:493

Used in: Filesystem

message GrpcServer

failure_details.proto:563

Used in: FailureDetail

enum GrpcServer.Code

failure_details.proto:564

Used in: GrpcServer

message HelpCommand

failure_details.proto:920

Used in: FailureDetail

enum HelpCommand.Code

failure_details.proto:921

Used in: HelpCommand

message IncludeScanning

failure_details.proto:763

Used in: FailureDetail

enum IncludeScanning.Code

failure_details.proto:764

Used in: IncludeScanning

message InfoCommand

failure_details.proto:615

Used in: FailureDetail

enum InfoCommand.Code

failure_details.proto:619

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: InfoCommand

message Interrupted

failure_details.proto:173

Used in: FailureDetail

enum Interrupted.Code

failure_details.proto:174

Used in: Interrupted

message JavaCompile

failure_details.proto:1014

Used in: FailureDetail

enum JavaCompile.Code

failure_details.proto:1015

Used in: JavaCompile

message LocalExecution

failure_details.proto:702

Used in: FailureDetail

enum LocalExecution.Code

failure_details.proto:703

Used in: LocalExecution

message LtoAction

failure_details.proto:1128

Used in: FailureDetail

enum LtoAction.Code

failure_details.proto:1129

Used in: LtoAction

message MemoryOptions

failure_details.proto:630

Used in: FailureDetail

enum MemoryOptions.Code

failure_details.proto:631

Used in: MemoryOptions

message MobileInstall

failure_details.proto:930

Used in: FailureDetail

enum MobileInstall.Code

failure_details.proto:931

Used in: MobileInstall

message ModqueryCommand

failure_details.proto:1304

Used in: FailureDetail

enum ModqueryCommand.Code

failure_details.proto:1305

Used in: ModqueryCommand

message NinjaAction

failure_details.proto:1066

Used in: FailureDetail

enum NinjaAction.Code

failure_details.proto:1067

Used in: NinjaAction

message PackageLoading

failure_details.proto:1203

Used in: FailureDetail

enum PackageLoading.Code

failure_details.proto:1204

Used in: IncludeScanning, PackageLoading

message PackageOptions

failure_details.proto:364

Used in: FailureDetail

enum PackageOptions.Code

failure_details.proto:365

Used in: PackageOptions

message PrintActionCommand

failure_details.proto:987

Used in: FailureDetail

enum PrintActionCommand.Code

failure_details.proto:988

Used in: PrintActionCommand

message ProfileCommand

failure_details.proto:944

Used in: FailureDetail

enum ProfileCommand.Code

failure_details.proto:945

Used in: ProfileCommand

message Query

failure_details.proto:643

Used in: FailureDetail

enum Query.Code

failure_details.proto:644

Used in: Query

message RemoteExecution

failure_details.proto:375

Used in: FailureDetail

enum RemoteExecution.Code

failure_details.proto:380

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: RemoteExecution

message RemoteOptions

failure_details.proto:286

Used in: FailureDetail

enum RemoteOptions.Code

failure_details.proto:287

Used in: RemoteOptions

message RunCommand

failure_details.proto:954

Used in: FailureDetail

enum RunCommand.Code

failure_details.proto:955

Used in: RunCommand

message Sandbox

failure_details.proto:744

Used in: FailureDetail

enum Sandbox.Code

failure_details.proto:745

Used in: Sandbox

message Spawn

failure_details.proto:207

Used in: FailureDetail

enum Spawn.Code

failure_details.proto:208

Used in: Spawn

message StarlarkAction

failure_details.proto:1056

Used in: FailureDetail

enum StarlarkAction.Code

failure_details.proto:1057

Used in: StarlarkAction

message StarlarkLoading

failure_details.proto:1264

Used in: FailureDetail

enum StarlarkLoading.Code

failure_details.proto:1265

Used in: StarlarkLoading

message SymlinkAction

failure_details.proto:1105

Used in: FailureDetail

enum SymlinkAction.Code

failure_details.proto:1106

Used in: SymlinkAction

message SymlinkForest

failure_details.proto:340

Used in: FailureDetail

enum SymlinkForest.Code

failure_details.proto:341

Used in: SymlinkForest

message SyncCommand

failure_details.proto:732

Used in: FailureDetail

enum SyncCommand.Code

failure_details.proto:733

Used in: SyncCommand

message TargetPatterns

failure_details.proto:829

Used in: FailureDetail

enum TargetPatterns.Code

failure_details.proto:830

Used in: TargetPatterns

message TestAction

failure_details.proto:1139

Used in: FailureDetail

enum TestAction.Code

failure_details.proto:1140

Used in: TestAction

message TestCommand

failure_details.proto:783

Used in: FailureDetail

enum TestCommand.Code

failure_details.proto:784

Used in: TestCommand

message Throwable

failure_details.proto:329

Used in: Crash

message Toolchain

failure_details.proto:1249

Used in: FailureDetail

enum Toolchain.Code

failure_details.proto:1250

Used in: Toolchain

message VersionCommand

failure_details.proto:978

Used in: FailureDetail

enum VersionCommand.Code

failure_details.proto:979

Used in: VersionCommand

message Worker

failure_details.proto:1152

Used in: FailureDetail

enum Worker.Code

failure_details.proto:1153

Used in: Worker

message WorkspaceStatus

failure_details.proto:999

Used in: FailureDetail

enum WorkspaceStatus.Code

failure_details.proto:1000

Used in: WorkspaceStatus

message Workspaces

failure_details.proto:466

Failure details about Bazel's WORKSPACE features.

Used in: FailureDetail

enum Workspaces.Code

failure_details.proto:467

Used in: Workspaces