Skip to content

Commit a8dd2bf

Browse files
committed
chore: increase Ginkgo sequential timeout slightly:
Signed-off-by: Jonathan West <jonwest@redhat.com>
1 parent 9d65e90 commit a8dd2bf

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

Makefile

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -169,7 +169,7 @@ e2e-tests-ginkgo: e2e-tests-sequential-ginkgo e2e-tests-parallel-ginkgo ## Runs
169169
.PHONY: e2e-tests-sequential-ginkgo
170170
e2e-tests-sequential-ginkgo: ginkgo ## Runs kuttl e2e sequential tests
171171
@echo "Running GitOps Operator sequential Ginkgo E2E tests..."
172-
$(GINKGO_CLI) -v --trace --timeout 120m -r ./test/openshift/e2e/ginkgo/sequential
172+
$(GINKGO_CLI) -v --trace --timeout 150m -r ./test/openshift/e2e/ginkgo/sequential
173173

174174
.PHONY: e2e-tests-parallel-ginkgo ## Runs kuttl e2e parallel tests, (Defaults to 5 runs at a time)
175175
e2e-tests-parallel-ginkgo: ginkgo

test/openshift/e2e/ginkgo/fixture/fixture.go

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -637,7 +637,8 @@ func WaitForAllDeploymentsInTheNamespaceToBeReady(ns string, k8sClient client.Cl
637637
// The above logic will successfully wait for Deployments to be ready. However, this does not mean that the operator's controller logic has completed it's initial cluster reconciliation logic (starting a watch then reconciling existing resources)
638638
// - I'm not aware of a way to detect when this has completed, so instead I am inserting a 15 second pause.
639639
// - If anyone has a better way of doing this, let us know.
640-
time.Sleep(15 * time.Second)
640+
// time.Sleep(15 * time.Second)
641+
// TODO: Uncomment this once the sequential test suite timeout has increased.
641642
}
642643

643644
func WaitForAllStatefulSetsInTheNamespaceToBeReady(ns string, k8sClient client.Client) {

0 commit comments

Comments
 (0)