Auto-update dependencies (#117)

Produced via:
  `dep ensure -update knative.dev/test-infra knative.dev/pkg`
/assign mattmoor

Gopkg.lock

@@ -927,7 +927,7 @@
 
 [[projects]]
   branch = "master"
-  digest = "1:2f0bfe47d6d494dfc206af0e4f4e7000db3fef052ed46026c4c6a2ba4c7cac32"
+  digest = "1:81b8fd15ad0e4a40172068f2e207d21c66fdce6f0d5fb37f340def04a5069382"
   name = "knative.dev/pkg"
   packages = [
     "apis",
@@ -946,18 +946,18 @@
     "metrics/metricskey",
   ]
   pruneopts = "T"
-  revision = "0b19b4ad91391699170edab6b36f7545c5ca6ead"
+  revision = "4befa47ec54be729c2ffd610513155892581b088"
 
 [[projects]]
   branch = "master"
-  digest = "1:0041ff0e6be31ac2cd85ffd4cf0b6ccb576b408d4f3c1c7e48c79cbf32a1319c"
+  digest = "1:988757b6c3d2df3248703c76ae0c63654319672fe368321a191cbbee88b12e69"
   name = "knative.dev/test-infra"
   packages = [
     "scripts",
     "tools/dep-collector",
   ]
   pruneopts = "UT"
-  revision = "8923e6806b082ebc75b5464ad23d9826f8eaa97b"
+  revision = "11b4f85e9c2714c45dda40abc5279b63f706f039"
 
 [[projects]]
   digest = "1:8730e0150dfb2b7e173890c8b9868e7a273082ef8e39f4940e3506a481cf895c"

vendor/knative.dev/pkg/Gopkg.lock

@@ -1260,14 +1260,14 @@
 
 [[projects]]
   branch = "master"
-  digest = "1:8009d9ea7464198279c5c1b1a760365c1f731aa88239632c08929df5b7f323f6"
+  digest = "1:0041ff0e6be31ac2cd85ffd4cf0b6ccb576b408d4f3c1c7e48c79cbf32a1319c"
   name = "knative.dev/test-infra"
   packages = [
     "scripts",
     "tools/dep-collector",
   ]
   pruneopts = "UT"
-  revision = "5d51ed40c38a606beaa42197961edb6d737227fc"
+  revision = "8923e6806b082ebc75b5464ad23d9826f8eaa97b"
 
 [[projects]]
   digest = "1:8730e0150dfb2b7e173890c8b9868e7a273082ef8e39f4940e3506a481cf895c"

vendor/knative.dev/pkg/apis/v1alpha1/destination.go

@@ -18,6 +18,7 @@ package v1alpha1
 
 import (
 	"context"
+
 	corev1 "k8s.io/api/core/v1"
 	"knative.dev/pkg/apis"
 )
@@ -50,15 +51,14 @@ func ValidateDestination(dest Destination) *apis.FieldError {
 	}
 	// IsAbs() check whether the URL has a non-empty scheme. Besides the non-empty scheme, we also require dest.URI has a non-empty host
 	if dest.Ref == nil && dest.URI != nil && (!dest.URI.URL().IsAbs() || dest.URI.Host == "") {
-			return apis.ErrInvalidValue("Relative URI is not allowed when Ref is absent",  "uri")
-		}
-	if dest.Ref != nil && dest.URI == nil{
+		return apis.ErrInvalidValue("Relative URI is not allowed when Ref is absent", "uri")
+	}
+	if dest.Ref != nil && dest.URI == nil {
 		return validateDestinationRef(*dest.Ref).ViaField("ref")
 	}
 	return nil
 }
 
-
 func validateDestinationRef(ref corev1.ObjectReference) *apis.FieldError {
 	// Check the object.
 	var errs *apis.FieldError

vendor/knative.dev/pkg/metrics/metricskey/constants_serving.go

@@ -53,8 +53,8 @@ var (
 	// KnativeRevisionMetrics stores a set of metric types which are supported
 	// by resource type knative_revision.
 	KnativeRevisionMetrics = sets.NewString(
-		"knative.dev/serving/activator/request_count",
-		"knative.dev/serving/activator/request_latencies",
+		"knative.dev/internal/serving/activator/request_count",
+		"knative.dev/internal/serving/activator/request_latencies",
 		"knative.dev/serving/autoscaler/desired_pods",
 		"knative.dev/serving/autoscaler/requested_pods",
 		"knative.dev/serving/autoscaler/actual_pods",
@@ -62,7 +62,7 @@ var (
 		"knative.dev/serving/autoscaler/panic_request_concurrency",
 		"knative.dev/serving/autoscaler/target_concurrency_per_pod",
 		"knative.dev/serving/autoscaler/panic_mode",
-		"knative.dev/serving/revision/request_count",
-		"knative.dev/serving/revision/request_latencies",
+		"knative.dev/internal/serving/revision/request_count",
+		"knative.dev/internal/serving/revision/request_latencies",
 	)
 )

vendor/knative.dev/pkg/test/zipkin/util.go

@@ -147,7 +147,7 @@ func JSONTrace(traceID string, expected int, timeout time.Duration) (trace []mod
 
 // TimeoutError is an error returned by JSONTrace if it times out before getting the expected number
 // of traces.
-type TimeoutError struct{
+type TimeoutError struct {
 	lastErr error
 }
 

vendor/knative.dev/pkg/testutils/clustermanager/prow-cluster-operation/README.md

@@ -1,7 +1,6 @@
 ## prow-cluster-operation
 
-prow-cluster-operation is a tool for creating, deleting, getting a GKE
-cluster
+prow-cluster-operation is a tool for creating, deleting, getting a GKE cluster
 
 ## Prerequisite
 
@@ -28,10 +27,12 @@ This tool can be invoked from command line with following parameters:
 
 1. Acquiring cluster if kubeconfig already points to it
 1. Get GCP project name if not provided as a parameter:
-    - [In Prow] Acquire from Boskos
-    - [Not in Prow] Read from gcloud config
 
-    Failed obtaining project name will fail the tool
+   - [In Prow] Acquire from Boskos
+   - [Not in Prow] Read from gcloud config
+
+   Failed obtaining project name will fail the tool
+
 1. Get default cluster name if not provided as a parameter
 1. Delete cluster if cluster with same name and location already exists in GKE
 1. Create cluster
@@ -43,8 +44,8 @@ This tool can be invoked from command line with following parameters:
 1. If cluster name is defined then getting cluster by its name
 1. If no cluster is found from previous step then it fails
 1. Delete:
-    - [In Prow] Release Boskos project
-    - [Not in Prow] Delete cluster
+   - [In Prow] Release Boskos project
+   - [Not in Prow] Delete cluster
 
 ### Get
 

vendor/knative.dev/test-infra/scripts/README.md

@@ -73,9 +73,9 @@ running the tests, and is automatically handled by the default action for
 integration tests (see above).
 
 To run a specific program as a test, use the `--run-test` flag, and provide the
-program as the argument. If arguments are required for the program, pass everything
-as a single quotes argument. For example, `./presubmit-tests.sh --run-test
-"test/my/test data"`.
+program as the argument. If arguments are required for the program, pass
+everything as a single quotes argument. For example,
+`./presubmit-tests.sh --run-test "test/my/test data"`.
 
 The script will automatically skip all presubmit tests for PRs where all changed
 files are exempt of tests (e.g., a PR changing only the `OWNERS` file).
@@ -243,23 +243,22 @@ benchmarking jobs for each repo. To use it:
    - `PROJECT_NAME`: GCP project name for keeping the clusters that run the
      benchmarks. Defaults to `knative-performance`.
    - `SERVICE_ACCOUNT_NAME`: Service account name for controlling GKE clusters
-     and interacting with [Mako](https://github.com/google/mako) server. It MUST have
-     `Kubernetes Engine Admin` and `Storage Admin` role, and be
+     and interacting with [Mako](https://github.com/google/mako) server. It MUST
+     have `Kubernetes Engine Admin` and `Storage Admin` role, and be
      [whitelisted](https://github.com/google/mako/blob/master/docs/ACCESS.md) by
      Mako admin. Defaults to `mako-job`.
 
 1. [optional] Customize root path of the benchmarks. This root folder should
-   contain and only contain all benchmarks you want to run continuously.
-   Set the following environment variable if the default value doesn't fit your
-   needs:
+   contain and only contain all benchmarks you want to run continuously. Set the
+   following environment variable if the default value doesn't fit your needs:
 
    - `BENCHMARK_ROOT_PATH`: Benchmark root path, defaults to
      `test/performance/benchmarks`. Each repo can decide which folder to put its
      benchmarks in, and override this environment variable to be the path of
      that folder.
 
-1. [optional] Write the `update_knative` function, which will update your
-   system under test (e.g. Knative Serving).
+1. [optional] Write the `update_knative` function, which will update your system
+   under test (e.g. Knative Serving).
 
 1. [optional] Write the `update_benchmark` function, which will update the
    underlying resources for the benchmark (usually Knative resources and