package failure_details

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

message ActionCache

failure_details.proto:729

Used in: FailureDetail

enum ActionCache.Code

failure_details.proto:730

Used in: ActionCache

message ActionQuery

failure_details.proto:814

Used in: FailureDetail

enum ActionQuery.Code

failure_details.proto:826

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

Used in: FailureDetail

enum ActionRewinding.Code

failure_details.proto:1046

Used in: ActionRewinding

message Analysis

failure_details.proto:1200

Used in: FailureDetail

enum Analysis.Code

failure_details.proto:1201

Used in: Analysis

message BuildConfiguration

failure_details.proto:605

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

Used in: BuildConfiguration

message BuildProgress

failure_details.proto:266

Used in: FailureDetail

enum BuildProgress.Code

failure_details.proto:267

Used in: BuildProgress

message BuildReport

failure_details.proto:357

Used in: FailureDetail

enum BuildReport.Code

failure_details.proto:358

Used in: BuildReport

message CanonicalizeFlags

failure_details.proto:591

Used in: FailureDetail

enum CanonicalizeFlags.Code

failure_details.proto:592

Used in: CanonicalizeFlags

message CleanCommand

failure_details.proto:874

Used in: FailureDetail

enum CleanCommand.Code

failure_details.proto:875

Used in: CleanCommand

message ClientEnvironment

failure_details.proto:308

Used in: FailureDetail

enum ClientEnvironment.Code

failure_details.proto:309

Used in: ClientEnvironment

message Command

failure_details.proto:553

Used in: FailureDetail

enum Command.Code

failure_details.proto:554

Used in: Command

message ConfigCommand

failure_details.proto:892

Used in: FailureDetail

enum ConfigCommand.Code

failure_details.proto:893

Used in: ConfigCommand

message ConfigurableQuery

failure_details.proto:902

Used in: FailureDetail

enum ConfigurableQuery.Code

failure_details.proto:903

Used in: ConfigurableQuery

message CppCompile

failure_details.proto:1063

Used in: FailureDetail

enum CppCompile.Code

failure_details.proto:1064

Used in: CppCompile

Used in: FailureDetail

enum CppLink.Code

failure_details.proto:1146

Used in: CppLink

message Crash

failure_details.proto:317

Used in: FailureDetail

enum Crash.Code

failure_details.proto:318

Used in: Crash

message CrashOptions

failure_details.proto:502

Used in: FailureDetail

enum CrashOptions.Code

failure_details.proto:503

Used in: CrashOptions

message DiffAwareness

failure_details.proto:1325

Used in: FailureDetail

enum DiffAwareness.Code

failure_details.proto:1326

Used in: DiffAwareness

message DumpCommand

failure_details.proto:923

Used in: FailureDetail

enum DumpCommand.Code

failure_details.proto:924

Used in: DumpCommand

message DynamicExecution

failure_details.proto:1102

Used in: FailureDetail

enum DynamicExecution.Code

failure_details.proto:1103

Used in: DynamicExecution

message Execution

failure_details.proto:437

Used in: FailureDetail

enum Execution.Code

failure_details.proto:438

Used in: Execution

message ExecutionOptions

failure_details.proto:528

Used in: FailureDetail

enum ExecutionOptions.Code

failure_details.proto:535

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

Used in: FailureDetail

enum ExternalDeps.Code

failure_details.proto:1311

Used in: ExternalDeps

message ExternalRepository

failure_details.proto:254

Used in: FailureDetail

enum ExternalRepository.Code

failure_details.proto:255

Used in: ExternalRepository

message FailAction

failure_details.proto:1114

Used in: FailureDetail

enum FailAction.Code

failure_details.proto:1115

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.BuildFinished, build_event_stream.TargetComplete, command_server.RunResponse

message FailureDetailMetadata

failure_details.proto:28

message FetchCommand

failure_details.proto:738

Used in: FailureDetail

enum FetchCommand.Code

failure_details.proto:739

Used in: FetchCommand

message Filesystem

failure_details.proto:511

Used in: FailureDetail

enum Filesystem.Code

failure_details.proto:512

Used in: Filesystem

message GrpcServer

failure_details.proto:578

Used in: FailureDetail

enum GrpcServer.Code

failure_details.proto:579

Used in: GrpcServer

message HelpCommand

failure_details.proto:940

Used in: FailureDetail

enum HelpCommand.Code

failure_details.proto:941

Used in: HelpCommand

message IncludeScanning

failure_details.proto:783

Used in: FailureDetail

enum IncludeScanning.Code

failure_details.proto:784

Used in: IncludeScanning

message InfoCommand

failure_details.proto:631

Used in: FailureDetail

enum InfoCommand.Code

failure_details.proto:635

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

Used in: FailureDetail

enum Interrupted.Code

failure_details.proto:176

Used in: Interrupted

message JavaCompile

failure_details.proto:1033

Used in: FailureDetail

enum JavaCompile.Code

failure_details.proto:1034

Used in: JavaCompile

message LocalExecution

failure_details.proto:719

Used in: FailureDetail

enum LocalExecution.Code

failure_details.proto:720

Used in: LocalExecution

message LtoAction

failure_details.proto:1155

Used in: FailureDetail

enum LtoAction.Code

failure_details.proto:1156

Used in: LtoAction

message MemoryOptions

failure_details.proto:646

Used in: FailureDetail

enum MemoryOptions.Code

failure_details.proto:647

Used in: MemoryOptions

message MobileInstall

failure_details.proto:950

Used in: FailureDetail

enum MobileInstall.Code

failure_details.proto:951

Used in: MobileInstall

message ModCommand

failure_details.proto:1334

Used in: FailureDetail

enum ModCommand.Code

failure_details.proto:1335

Used in: ModCommand

message NinjaAction

failure_details.proto:1092

Used in: FailureDetail

enum NinjaAction.Code

failure_details.proto:1093

Used in: NinjaAction

message PackageLoading

failure_details.proto:1232

Used in: FailureDetail

enum PackageLoading.Code

failure_details.proto:1233

Used in: IncludeScanning, PackageLoading

message PackageOptions

failure_details.proto:396

Used in: FailureDetail

enum PackageOptions.Code

failure_details.proto:397

Used in: PackageOptions

message PrintActionCommand

failure_details.proto:1006

Used in: FailureDetail

enum PrintActionCommand.Code

failure_details.proto:1007

Used in: PrintActionCommand

message ProfileCommand

failure_details.proto:964

Used in: FailureDetail

enum ProfileCommand.Code

failure_details.proto:965

Used in: ProfileCommand

message Query

failure_details.proto:664

Used in: FailureDetail

enum Query.Code

failure_details.proto:665

Used in: Query

message RemoteAnalysisCaching

failure_details.proto:386

Failure details for errors produced during remote analysis caching.

Used in: FailureDetail

enum RemoteAnalysisCaching.Code

failure_details.proto:387

Used in: RemoteAnalysisCaching

message RemoteExecution

failure_details.proto:408

Used in: FailureDetail

enum RemoteExecution.Code

failure_details.proto:413

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

Used in: FailureDetail

enum RemoteOptions.Code

failure_details.proto:292

Used in: RemoteOptions

message RunCommand

failure_details.proto:974

Used in: FailureDetail

enum RunCommand.Code

failure_details.proto:975

Used in: RunCommand

message Sandbox

failure_details.proto:762

Used in: FailureDetail

enum Sandbox.Code

failure_details.proto:763

Used in: Sandbox

message Skyfocus

failure_details.proto:370

Failure details for errors produced when using Skyfocus

Used in: FailureDetail

enum Skyfocus.Code

failure_details.proto:371

Used in: Skyfocus

message Spawn

failure_details.proto:209

Used in: FailureDetail

enum Spawn.Code

failure_details.proto:210

Used in: Spawn

message StarlarkAction

failure_details.proto:1082

Used in: FailureDetail

enum StarlarkAction.Code

failure_details.proto:1083

Used in: StarlarkAction

message StarlarkLoading

failure_details.proto:1292

Used in: FailureDetail

enum StarlarkLoading.Code

failure_details.proto:1293

Used in: StarlarkLoading

message SymlinkAction

failure_details.proto:1131

Used in: FailureDetail

enum SymlinkAction.Code

failure_details.proto:1132

Used in: SymlinkAction

message SymlinkForest

failure_details.proto:346

Used in: FailureDetail

enum SymlinkForest.Code

failure_details.proto:347

Used in: SymlinkForest

message SyncCommand

failure_details.proto:750

Used in: FailureDetail

enum SyncCommand.Code

failure_details.proto:751

Used in: SyncCommand

message TargetPatterns

failure_details.proto:847

Used in: FailureDetail

enum TargetPatterns.Code

failure_details.proto:848

Used in: TargetPatterns

message TestAction

failure_details.proto:1166

Used in: FailureDetail

enum TestAction.Code

failure_details.proto:1167

Used in: TestAction

message TestCommand

failure_details.proto:803

Used in: FailureDetail

enum TestCommand.Code

failure_details.proto:804

Used in: TestCommand

message Throwable

failure_details.proto:335

Used in: Crash

message Toolchain

failure_details.proto:1277

Used in: FailureDetail

enum Toolchain.Code

failure_details.proto:1278

Used in: Toolchain

message VersionCommand

failure_details.proto:997

Used in: FailureDetail

enum VersionCommand.Code

failure_details.proto:998

Used in: VersionCommand

message Worker

failure_details.proto:1179

Used in: FailureDetail

enum Worker.Code

failure_details.proto:1180

Used in: build_event_stream.BuildMetrics.WorkerMetrics, Worker

message WorkspaceStatus

failure_details.proto:1018

Used in: FailureDetail

enum WorkspaceStatus.Code

failure_details.proto:1019

Used in: WorkspaceStatus

message Workspaces

failure_details.proto:487

Failure details about Bazel's WORKSPACE features.

Used in: FailureDetail

enum Workspaces.Code

failure_details.proto:488

Used in: Workspaces