Class: Google::Apis::RemotebuildexecutionV2::GoogleDevtoolsRemoteexecutionV1testExecuteResponse

Inherits:
Object
  • Object
show all
Includes:
Core::Hashable, Core::JsonObjectSupport
Defined in:
generated/google/apis/remotebuildexecution_v2/classes.rb,
generated/google/apis/remotebuildexecution_v2/representations.rb,
generated/google/apis/remotebuildexecution_v2/representations.rb

Overview

The response message for Execution.Execute, which will be contained in the response field of the Operation.

Instance Attribute Summary collapse

Instance Method Summary collapse

Methods included from Core::JsonObjectSupport

#to_json

Methods included from Core::Hashable

process_value, #to_h

Constructor Details

#initialize(**args) ⇒ GoogleDevtoolsRemoteexecutionV1testExecuteResponse

Returns a new instance of GoogleDevtoolsRemoteexecutionV1testExecuteResponse



3284
3285
3286
 
# File 'generated/google/apis/remotebuildexecution_v2/classes.rb', line 3284

def initialize(**args)
   update!(**args)
end

Instance Attribute Details

#cached_result ⇒ Boolean Also known as: cached_result?

True if the result was served from cache, false if it was executed. Corresponds to the JSON property cachedResult

Returns:

  • (Boolean) 


3221
3222
3223
 
# File 'generated/google/apis/remotebuildexecution_v2/classes.rb', line 3221

def cached_result
  @cached_result
end

#result ⇒ Google::Apis::RemotebuildexecutionV2::GoogleDevtoolsRemoteexecutionV1testActionResult

An ActionResult represents the result of an Action being run. Corresponds to the JSON property result

Returns:



3228
3229
3230
 
# File 'generated/google/apis/remotebuildexecution_v2/classes.rb', line 3228

def result
  @result
end

#server_logs ⇒ Hash<String,Google::Apis::RemotebuildexecutionV2::GoogleDevtoolsRemoteexecutionV1testLogFile>

An optional list of additional log outputs the server wishes to provide. A server can use this to return execution-specific logs however it wishes. This is intended primarily to make it easier for users to debug issues that may be outside of the actual job execution, such as by identifying the worker executing the action or by providing logs from the worker's setup phase. The keys SHOULD be human readable so that a client can display them to a user. Corresponds to the JSON property serverLogs

Returns:



3239
3240
3241
 
# File 'generated/google/apis/remotebuildexecution_v2/classes.rb', line 3239

def server_logs
  @server_logs
end

#status ⇒ Google::Apis::RemotebuildexecutionV2::GoogleRpcStatus

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. The error model is designed to be:

  • Simple to use and understand for most users
  • Flexible enough to meet unexpected needs # Overview The Status message contains three pieces of data: error code, error message, and error details. The error code should be an enum value of google.rpc.Code, but it may accept additional error codes if needed. The error message should be a developer-facing English message that helps developers understand and resolve the error. If a localized user-facing error message is needed, put the localized message in the error details or localize it in the client. The optional error details may contain arbitrary information about the error. There is a predefined set of error detail types in the package google.rpc that can be used for common error conditions. # Language mapping The Status message is the logical representation of the error model, but it is not necessarily the actual wire format. When the Status message is exposed in different client libraries and different wire protocols, it can be mapped differently. For example, it will likely be mapped to some exceptions in Java, but more likely mapped to some error codes in C. # Other uses The error model and the Status message can be used in a variety of environments, either with or without APIs, to provide a consistent developer experience across different environments. Example uses of this error model include:
  • Partial errors. If a service needs to return partial errors to the client, it may embed the Status in the normal response to indicate the partial errors.
  • Workflow errors. A typical workflow has multiple steps. Each step may have a Status message for error reporting.
  • Batch operations. If a client uses batch request and batch response, the Status message should be used directly inside batch response, one for each error sub-response.
  • Asynchronous operations. If an API call embeds asynchronous operation results in its response, the status of those operations should be represented directly using the Status message.
  • Logging. If some API errors are stored in logs, the message Status could be used directly after any stripping needed for security/privacy reasons. Corresponds to the JSON property status

Returns:



3282
3283
3284
 
# File 'generated/google/apis/remotebuildexecution_v2/classes.rb', line 3282

def status
  @status
end

Instance Method Details

#update!(**args) ⇒ Object

Update properties of this object



3289
3290
3291
3292
3293
3294
 
# File 'generated/google/apis/remotebuildexecution_v2/classes.rb', line 3289

def update!(**args)
  @cached_result = args[:cached_result] if args.key?(:cached_result)
  @result = args[:result] if args.key?(:result)
  @server_logs = args[:server_logs] if args.key?(:server_logs)
  @status = args[:status] if args.key?(:status)
end