Api-Roll 52: 2017-07-31

discovery/googleapis_beta/toolresults__v1beta3.json

 {
     "auth": {
         "oauth2": {
             "scopes": {
                 "https://www.googleapis.com/auth/cloud-platform": {
                     "description": "View and manage your data across Google Cloud Platform services"
                 }
             }
         }
     },
     "basePath": "/toolresults/v1beta3/projects/",
     "baseUrl": "https://www.googleapis.com/toolresults/v1beta3/projects/",
     "batchPath": "batch",
     "canonicalName": "Tool Results",
     "description": "Reads and publishes results from Firebase Test Lab.",
     "discoveryVersion": "v1",
     "documentationLink": "https://firebase.google.com/docs/test-lab/",
-    "etag": "\"YWOzh2SDasdU84ArJnpYek-OMdg/KPoCZlZv0v6Eoa2JwEmeeev_-W0\"",
+    "etag": "\"YWOzh2SDasdU84ArJnpYek-OMdg/ZyI2MKAoJf8XY5sH6nCuoCwniOY\"",
     "icons": {
         "x16": "https://www.gstatic.com/images/branding/product/1x/googleg_16dp.png",
         "x32": "https://www.gstatic.com/images/branding/product/1x/googleg_32dp.png"
     },
     "id": "toolresults:v1beta3",
     "kind": "discovery#restDescription",
     "name": "toolresults",
     "ownerDomain": "google.com",
     "ownerName": "Google",
     "parameters": {
@@ skipping 1046 matching lines @@
                                         }
                                     }
                                 }
                             }
                         }
                     }
                 }
             }
         }
     },
-    "revision": "20170707",
+    "revision": "20170727",
     "rootUrl": "https://www.googleapis.com/",
     "schemas": {
         "Any": {
             "description": "`Any` contains an arbitrary serialized protocol buffer message along with a URL that describes the type of the serialized message.\n\nProtobuf library provides support to pack/unpack Any values in the form of utility functions or additional generated methods of the Any type.\n\nExample 1: Pack and unpack a message in C++.\n\nFoo foo = ...; Any any; any.PackFrom(foo); ... if (any.UnpackTo(&foo)) { ... }\n\nExample 2: Pack and unpack a message in Java.\n\nFoo foo = ...; Any any = Any.pack(foo); ... if (any.is(Foo.class)) { foo = any.unpack(Foo.class); }\n\nExample 3: Pack and unpack a message in Python.\n\nfoo = Foo(...) any = Any() any.Pack(foo) ... if any.Is(Foo.DESCRIPTOR): any.Unpack(foo) ...\n\nExample 4: Pack and unpack a message in Go\n\nfoo := &pb.Foo{...} any, err := ptypes.MarshalAny(foo) ... foo := &pb.Foo{} if err := ptypes.UnmarshalAny(any, foo); err != nil { ... }\n\nThe pack methods provided by protobuf library will by default use 'type.googleapis.com/full.type.name' as the type URL and the unpack methods only use the fully qualified type name after the last '/' in the type URL, for example \"foo.bar.com/x/y.z\" will yield type name \"y.z\".\n\n\n\nJSON ==== The JSON representation of an `Any` value uses the regular representation of the deserialized, embedded message, with an additional field `@type` which contains the type URL. Example:\n\npackage google.profile; message Person { string first_name = 1; string last_name = 2; }\n\n{ \"@type\": \"type.googleapis.com/google.profile.Person\", \"firstName\": , \"lastName\":  }\n\nIf the embedded message type is well-known and has a custom JSON representation, that representation will be embedded adding a field `value` which holds the custom JSON in addition to the `@type` field. Example (for message [google.protobuf.Duration][]):\n\n{ \"@type\": \"type.googleapis.com/google.protobuf.Duration\", \"value\": \"1.212s\" }",
             "id": "Any",
             "properties": {
                 "typeUrl": {
                     "description": "A URL/resource name whose content describes the type of the serialized protocol buffer message.\n\nFor URLs which use the scheme `http`, `https`, or no scheme, the following restrictions and interpretations apply:\n\n* If no scheme is provided, `https` is assumed. * The last segment of the URL's path must represent the fully qualified name of the type (as in `path/google.protobuf.Duration`). The name should be in a canonical form (e.g., leading \".\" is not accepted). * An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)\n\nSchemes other than `http`, `https` (or the empty scheme) might be used with implementation specific semantics.",
                     "type": "string"
                 },
@@ skipping 188 matching lines @@
                     ],
                     "enumDescriptions": [
                         "",
                         "",
                         "",
                         ""
                     ],
                     "type": "string"
                 },
                 "testExecutionMatrixId": {
-                    "description": "TestExecution Matrix ID that the Test Service uses.\n\n- In response: present if set by create - In create: optional - In update: never set",
+                    "description": "TestExecution Matrix ID that the TestExecutionService uses.\n\n- In response: present if set by create - In create: optional - In update: never set",
                     "type": "string"
                 }
             },
             "type": "object"
         },
         "FailureDetail": {
             "id": "FailureDetail",
             "properties": {
                 "crashed": {
                     "description": "If the failure was severe because the system under test crashed.",
@@ skipping 399 matching lines @@
                     "description": "If the requested OS version doesn't run on the specific device model.",
                     "type": "boolean"
                 }
             },
             "type": "object"
         },
         "StackTrace": {
             "description": "A stacktrace.",
             "id": "StackTrace",
             "properties": {
+                "clusterId": {
+                    "description": "Exception cluster ID",
+                    "type": "string"
+                },
                 "exception": {
                     "description": "The stack trace message.\n\nRequired",
                     "type": "string"
+                },
+                "reportId": {
+                    "description": "Exception report ID",
+                    "type": "string"
                 }
             },
             "type": "object"
         },
         "Status": {
             "description": "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](https://github.com/grpc). The error model is designed to be:\n\n- Simple to use and understand for most users - Flexible enough to meet unexpected needs\n\n# Overview\n\nThe `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.\n\n# Language mapping\n\nThe `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.\n\n# Other uses\n\nThe 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.\n\nExample uses of this error model include:\n\n- 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.\n\n- Workflow errors. A typical workflow has multiple steps. Each step may have a `Status` message for error reporting.\n\n- 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.\n\n- 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.\n\n- Logging. If some API errors are stored in logs, the message `Status` could be used directly after any stripping needed for security/privacy reasons.",
             "id": "Status",
             "properties": {
                 "code": {
                     "description": "The status code, which should be an enum value of [google.rpc.Code][].",
@@ skipping 353 matching lines @@
                     "description": "The test case to which this output file belongs.\n\n- In response: present if set by create/update request - In create/update request: optional"
                 }
             },
             "type": "object"
         }
     },
     "servicePath": "toolresults/v1beta3/projects/",
     "title": "Cloud Tool Results API",
     "version": "v1beta3"
 }