From b6dd1ffd24a5f99cd03e18685bae3bc09ee1453c Mon Sep 17 00:00:00 2001 From: Suraj Deshmukh Date: Tue, 17 Mar 2020 18:49:39 +0530 Subject: [PATCH] e2e tests: Increase the test timeout to 20m Signed-off-by: Suraj Deshmukh --- Makefile | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Makefile b/Makefile index 1483e40dd..8e18a68ec 100644 --- a/Makefile +++ b/Makefile @@ -88,12 +88,12 @@ endif .PHONY: run-e2e-tests run-e2e-tests: - KUBECONFIG=${kubeconfig} go test -mod=$(MOD) -tags="$(platform),e2e" -covermode=atomic -buildmode=exe -v ./test/... + KUBECONFIG=${kubeconfig} go test -timeout=20m -mod=$(MOD) -tags="$(platform),e2e" -covermode=atomic -buildmode=exe -v ./test/... # Test if the metrics are actually being scraped - KUBECONFIG=${kubeconfig} PLATFORM=${platform} go test -mod=$(MOD) -tags="$(platform),poste2e" -covermode=atomic -buildmode=exe -v ./test/... + KUBECONFIG=${kubeconfig} PLATFORM=${platform} go test -timeout=20m -mod=$(MOD) -tags="$(platform),poste2e" -covermode=atomic -buildmode=exe -v ./test/... # This is a test that should be run in the end to reduce the disruption to other tests because # it will delete a node. - KUBECONFIG=${kubeconfig} go test -mod=$(MOD) -tags="$(platform),disruptivee2e" -covermode=atomic -buildmode=exe -v ./test/... + KUBECONFIG=${kubeconfig} go test -timeout=20m -mod=$(MOD) -tags="$(platform),disruptivee2e" -covermode=atomic -buildmode=exe -v ./test/... .PHONY: all all: build test