From cfc77970237363db267089859780eae518fc1410 Mon Sep 17 00:00:00 2001 From: Davanum Srinivas Date: Mon, 15 Oct 2018 13:13:12 -0400 Subject: [PATCH] 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 --- build/lib/release.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build/lib/release.sh b/build/lib/release.sh index 5682c700f9e..096ab36eb2d 100644 --- a/build/lib/release.sh +++ b/build/lib/release.sh @@ -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 #