Switch off KUBE_BUILD_CONFORMANCE to diagnose a ci-cross issue

Looking at job results, there seems to be some flakiness, let's see if
the PR that added the conformance image is the one to blame.

https://prow.k8s.io/?type=periodic&job=ci-kubernetes-cross-build
https://k8s-testgrid.appspot.com/sig-release-misc#cross-build&graph-metrics=test-duration-minutes&width=20

Change-Id: Ic26431a0e262100dec0444279d94277482972b07
This commit is contained in:
Davanum Srinivas 2018-10-15 13:13:12 -04:00
parent 8928e70af9
commit cfc7797023
No known key found for this signature in database
GPG Key ID: 80D83A796103BF59

View File

@ -29,7 +29,7 @@ readonly RELEASE_TARS="${LOCAL_OUTPUT_ROOT}/release-tars"
readonly RELEASE_IMAGES="${LOCAL_OUTPUT_ROOT}/release-images"
KUBE_BUILD_HYPERKUBE=${KUBE_BUILD_HYPERKUBE:-y}
KUBE_BUILD_CONFORMANCE=${KUBE_BUILD_CONFORMANCE:-y}
KUBE_BUILD_CONFORMANCE=${KUBE_BUILD_CONFORMANCE:-n}
# Validate a ci version
#