class Google::Apis::RemotebuildexecutionV2::BuildBazelRemoteExecutionV2ActionResult

An ActionResult represents the result of an Action being run. It is advised that at least one field (for example `ActionResult.execution_metadata.Worker`) have a non-default value, to ensure that the serialized value is non-empty, which can then be used as a basic data sanity check.

Attributes

execution_metadata[RW]

ExecutedActionMetadata contains details about a completed execution. Corresponds to the JSON property `executionMetadata` @return [Google::Apis::RemotebuildexecutionV2::BuildBazelRemoteExecutionV2ExecutedActionMetadata]

exit_code[RW]

The exit code of the command. Corresponds to the JSON property `exitCode` @return [Fixnum]

output_directories[RW]

The output directories of the action. For each output directory requested in the `output_directories` or `output_paths` field of the Action, if the corresponding directory existed after the action completed, a single entry will be present in the output list, which will contain the digest of a Tree message containing the directory tree, and the path equal exactly to the corresponding Action output_directories member. As an example, suppose the Action had an output directory `a/b/dir` and the execution produced the following contents in `a/b/dir`: a file named `bar` and a directory named `foo` with an executable file named `baz`. Then, output_directory will contain ( hashes shortened for readability): “`json // OutputDirectory proto: ` path: “ a/b/dir” tree_digest: ` hash: “4a73bc9d03…”, size: 55 ` ` // Tree proto with hash “4a73bc9d03…” and size 55: ` root: ` files: [ ` name: “bar”, digest: ` hash: “4a73bc9d03…”, size: 65534 ` ` ], directories: [ ` name: “foo”, digest: ` hash: “4cf2eda940…”, size: 43 ` ` ] ` children : ` // (Directory proto with hash “4cf2eda940…” and size 43) files: [ ` name: “baz”, digest: ` hash: “b2c941073e…”, size: 1294, `, is_executable: true ` ] ` ` “` If an output of the same name as listed in `output_files` of the Command was found in ` output_directories`, but was not a directory, the server will return a FAILED_PRECONDITION. Corresponds to the JSON property `outputDirectories` @return [Array<Google::Apis::RemotebuildexecutionV2::BuildBazelRemoteExecutionV2OutputDirectory>]

output_files[RW]

The output files of the action. For each output file requested in the ` output_files` or `output_paths` field of the Action, if the corresponding file existed after the action completed, a single entry will be present either in this field, or the `output_file_symlinks` field if the file was a symbolic link to another file (`output_symlinks` field after v2.1). If an output listed in `output_files` was found, but was a directory rather than a regular file, the server will return a FAILED_PRECONDITION. If the action does not produce the requested output, then that output will be omitted from the list. The server is free to arrange the output list as desired; clients MUST NOT assume that the output list is sorted. Corresponds to the JSON property `outputFiles` @return [Array<Google::Apis::RemotebuildexecutionV2::BuildBazelRemoteExecutionV2OutputFile>]

stderr_digest[RW]

A content digest. A digest for a given blob consists of the size of the blob and its hash. The hash algorithm to use is defined by the server. The size is considered to be an integral part of the digest and cannot be separated. That is, even if the `hash` field is correctly specified but `size_bytes` is not, the server MUST reject the request. The reason for including the size in the digest is as follows: in a great many cases, the server needs to know the size of the blob it is about to work with prior to starting an operation with it, such as flattening Merkle tree structures or streaming it to a worker. Technically, the server could implement a separate metadata store, but this results in a significantly more complicated implementation as opposed to having the client specify the size up-front (or storing the size along with the digest in every message where digests are embedded). This does mean that the API leaks some implementation details of (what we consider to be) a reasonable server implementation, but we consider this to be a worthwhile tradeoff. When a `Digest` is used to refer to a proto message, it always refers to the message in binary encoded form. To ensure consistent hashing, clients and servers MUST ensure that they serialize messages according to the following rules, even if there are alternate valid encodings for the same message: * Fields are serialized in tag order. * There are no unknown fields. * There are no duplicate fields. * Fields are serialized according to the default semantics for their type. Most protocol buffer implementations will always follow these rules when serializing, but care should be taken to avoid shortcuts. For instance, concatenating two messages to merge them may produce duplicate fields. Corresponds to the JSON property `stderrDigest` @return [Google::Apis::RemotebuildexecutionV2::BuildBazelRemoteExecutionV2Digest]

stderr_raw[RW]

The standard error buffer of the action. The server SHOULD NOT inline stderr unless requested by the client in the GetActionResultRequest message. The server MAY omit inlining, even if requested, and MUST do so if inlining would cause the response to exceed message size limits. Corresponds to the JSON property `stderrRaw` NOTE: Values are automatically base64 encoded/decoded in the client library. @return [String]

stdout_digest[RW]

A content digest. A digest for a given blob consists of the size of the blob and its hash. The hash algorithm to use is defined by the server. The size is considered to be an integral part of the digest and cannot be separated. That is, even if the `hash` field is correctly specified but `size_bytes` is not, the server MUST reject the request. The reason for including the size in the digest is as follows: in a great many cases, the server needs to know the size of the blob it is about to work with prior to starting an operation with it, such as flattening Merkle tree structures or streaming it to a worker. Technically, the server could implement a separate metadata store, but this results in a significantly more complicated implementation as opposed to having the client specify the size up-front (or storing the size along with the digest in every message where digests are embedded). This does mean that the API leaks some implementation details of (what we consider to be) a reasonable server implementation, but we consider this to be a worthwhile tradeoff. When a `Digest` is used to refer to a proto message, it always refers to the message in binary encoded form. To ensure consistent hashing, clients and servers MUST ensure that they serialize messages according to the following rules, even if there are alternate valid encodings for the same message: * Fields are serialized in tag order. * There are no unknown fields. * There are no duplicate fields. * Fields are serialized according to the default semantics for their type. Most protocol buffer implementations will always follow these rules when serializing, but care should be taken to avoid shortcuts. For instance, concatenating two messages to merge them may produce duplicate fields. Corresponds to the JSON property `stdoutDigest` @return [Google::Apis::RemotebuildexecutionV2::BuildBazelRemoteExecutionV2Digest]

stdout_raw[RW]

The standard output buffer of the action. The server SHOULD NOT inline stdout unless requested by the client in the GetActionResultRequest message. The server MAY omit inlining, even if requested, and MUST do so if inlining would cause the response to exceed message size limits. Corresponds to the JSON property `stdoutRaw` NOTE: Values are automatically base64 encoded/decoded in the client library. @return [String]

Public Class Methods

new(**args) click to toggle source
# File lib/google/apis/remotebuildexecution_v2/classes.rb, line 353
def initialize(**args)
   update!(**args)
end

Public Instance Methods

update!(**args) click to toggle source

Update properties of this object

# File lib/google/apis/remotebuildexecution_v2/classes.rb, line 358
def update!(**args)
  @execution_metadata = args[:execution_metadata] if args.key?(:execution_metadata)
  @exit_code = args[:exit_code] if args.key?(:exit_code)
  @output_directories = args[:output_directories] if args.key?(:output_directories)
  @output_directory_symlinks = args[:output_directory_symlinks] if args.key?(:output_directory_symlinks)
  @output_file_symlinks = args[:output_file_symlinks] if args.key?(:output_file_symlinks)
  @output_files = args[:output_files] if args.key?(:output_files)
  @output_symlinks = args[:output_symlinks] if args.key?(:output_symlinks)
  @stderr_digest = args[:stderr_digest] if args.key?(:stderr_digest)
  @stderr_raw = args[:stderr_raw] if args.key?(:stderr_raw)
  @stdout_digest = args[:stdout_digest] if args.key?(:stdout_digest)
  @stdout_raw = args[:stdout_raw] if args.key?(:stdout_raw)
end