Flaky build tests for triggers

[CarolynMabbott]

The pull-tekton-triggers-build-tests are flaky
I did a PR for a README change and the test failed in the linting part

--------------------------------
I1223 14:12:04.472] ---- Linting the yaml files ----
I1223 14:12:04.473] --------------------------------
I1223 14:14:40.214] level=warning msg="[runner] Can't run linter goanalysis_metalinter: ctrlflow: failed prerequisites: inspect@github.com/tektoncd/triggers/test/builder [github.com/tektoncd/triggers/pkg/apis/triggers/v1alpha1.test]"
I1223 14:14:40.216] level=error msg="Timeout exceeded: try increase it by passing --timeout option"
I1223 14:14:40.409] Diffing against the documentation yaml
I1223 14:14:40.626] ============================
I1223 14:14:40.626] ==== BUILD TESTS FAILED ====
I1223 14:14:40.627] ============================
W1223 14:14:40.727] Run: ('/workspace/./test-infra/jenkins/../scenarios/../hack/coalesce.py',)
E1223 14:14:40.920] Command failed
I1223 14:14:40.920] process 467 exited with code 1 after 2.8m
E1223 14:14:40.921] FAIL: pull-tekton-triggers-build-tests

============================
I1223 14:11:56.417] ==== CURRENT TEST SETUP ====
I1223 14:11:56.417] ============================
I1223 14:11:56.417] >> gcloud SDK version
I1223 14:11:56.681] Google Cloud SDK 274.0.0
I1223 14:11:56.681] alpha 2019.05.17
I1223 14:11:56.681] beta 2019.05.17
I1223 14:11:56.682] bq 2.0.51
I1223 14:11:56.682] core 2019.12.17
I1223 14:11:56.682] docker-credential-gcr 
I1223 14:11:56.682] gsutil 4.46
I1223 14:11:56.682] kubectl 2019.11.04
I1223 14:11:56.716] >> kubectl version
I1223 14:11:56.821] Client Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.11-dispatcher", GitCommit:"2e298c7e992f83f47af60cf4830b11c7370f6668", GitTreeState:"clean", BuildDate:"2019-09-19T22:20:12Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}
I1223 14:11:56.825] >> go version
I1223 14:11:56.831] go version go1.13 linux/amd64
I1223 14:11:56.832] >> git version
I1223 14:11:56.834] git version 2.11.0
I1223 14:11:56.834] >> bazel version
I1223 14:12:04.169] Build label: 0.28.1
I1223 14:12:04.169] Build target: bazel-out/k8-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
I1223 14:12:04.170] Build time: Fri Jul 19 15:19:51 2019 (1563549591)
I1223 14:12:04.171] Build timestamp: 1563549591
I1223 14:12:04.171] Build timestamp as int: 1563549591
I1223 14:12:04.215] =============================
I1223 14:12:04.215] ==== RUNNING BUILD TESTS ====
I1223 14:12:04.216] =============================
I1223 14:12:04.218] -------------------------------------------
I1223 14:12:04.218] ---- Checking go code style with gofmt ----
I1223 14:12:04.218] -------------------------------------------
I1223 14:12:04.471] 
I1223 14:12:04.471] --------------------------------
I1223 14:12:04.472] ---- Linting the yaml files ----
I1223 14:12:04.473] --------------------------------
I1223 14:14:40.214] level=warning msg="[runner] Can't run linter goanalysis_metalinter: ctrlflow: failed prerequisites: inspect@github.com/tektoncd/triggers/test/builder [github.com/tektoncd/triggers/pkg/apis/triggers/v1alpha1.test]"
I1223 14:14:40.216] level=error msg="Timeout exceeded: try increase it by passing --timeout option"
I1223 14:14:40.409] Diffing against the documentation yaml
I1223 14:14:40.626] ============================
I1223 14:14:40.626] ==== BUILD TESTS FAILED ====
I1223 14:14:40.627] ============================
W1223 14:14:40.727] Run: ('/workspace/./test-infra/jenkins/../scenarios/../hack/coalesce.py',)
E1223 14:14:40.920] Command failed
I1223 14:14:40.920] process 467 exited with code 1 after 2.8m
E1223 14:14:40.921] FAIL: pull-tekton-triggers-build-tests
I1223 14:14:40.921] Call:  gcloud auth activate-service-account --key-file=/etc/test-account/service-account.json
W1223 14:14:41.768] Activated service account credentials for: [prow-account@tekton-releases.iam.gserviceaccount.com]
I1223 14:14:41.870] process 4400 exited with code 0 after 0.0m
I1223 14:14:41.871] Call:  gcloud config get-value account
I1223 14:14:42.358] process 4413 exited with code 0 after 0.0m
I1223 14:14:42.359] Will upload results to gs://tekton-prow/pr-logs using prow-account@tekton-releases.iam.gserviceaccount.com
I1223 14:14:42.359] Upload result and artifacts...
I1223 14:14:42.360] Gubernator results at https://gubernator.k8s.io/build/tekton-prow/pr-logs/pull/tektoncd_triggers/297/pull-tekton-triggers-build-tests/1209114294101217283
I1223 14:14:42.361] Call:  gsutil ls gs://tekton-prow/pr-logs/pull/tektoncd_triggers/297/pull-tekton-triggers-build-tests/1209114294101217283/artifacts
W1223 14:14:44.036] CommandException: One or more URLs matched no objects.
E1223 14:14:44.214] Command failed
I1223 14:14:44.215] process 4426 exited with code 1 after 0.0m
W1223 14:14:44.215] Remote dir gs://tekton-prow/pr-logs/pull/tektoncd_triggers/297/pull-tekton-triggers-build-tests/1209114294101217283/artifacts not exist yet
I1223 14:14:44.215] Call:  gsutil -m -q -o GSUtil:use_magicfile=True cp -r -c -z log,txt,xml /workspace/_artifacts gs://tekton-prow/pr-logs/pull/tektoncd_triggers/297/pull-tekton-triggers-build-tests/1209114294101217283/artifacts

Reran the tests and it passed so appears to be a flaky test

[vdemeester]

/area test-infra
/kind flake

Sometimes, the linter times out… most likely when the node it runs in is a bit under load…

I1223 14:12:04.472] ---- Linting the yaml files ----
I1223 14:12:04.473] --------------------------------
I1223 14:14:40.214] level=warning msg="[runner] Can't run linter goanalysis_metalinter: ctrlflow: failed prerequisites: inspect@github.com/tektoncd/triggers/test/builder [github.com/tektoncd/triggers/pkg/apis/triggers/v1alpha1.test]"
I1223 14:14:40.216] level=error msg="Timeout exceeded: try increase it by passing --timeout option"
I1223 14:14:40.409] Diffing against the documentation yaml

[bobcatfish]

Closing this in favor of tektoncd/plumbing#241