From f41a169a354ff72f324e5fc0584126ed1a8a5b69 Mon Sep 17 00:00:00 2001 From: Patrick Ohly Date: Tue, 23 May 2023 08:29:10 +0200 Subject: [PATCH] e2e: apply timeout for CSI Storage Capacity test only to node Applying it to the entire spec included cleaning up, which makes predicting the acceptable duration harder because it includes code not owned by the test itself. It's better to specify a timeout only for the test code itself. --- test/e2e/storage/csi_mock/csi_storage_capacity.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/e2e/storage/csi_mock/csi_storage_capacity.go b/test/e2e/storage/csi_mock/csi_storage_capacity.go index 52d79259a79..5a171b25198 100644 --- a/test/e2e/storage/csi_mock/csi_storage_capacity.go +++ b/test/e2e/storage/csi_mock/csi_storage_capacity.go @@ -320,7 +320,7 @@ var _ = utils.SIGDescribe("CSI Mock volume storage capacity", func() { } for _, t := range tests { test := t - ginkgo.It(t.name, ginkgo.SpecTimeout(f.Timeouts.PodStart), func(ctx context.Context) { + ginkgo.It(t.name, ginkgo.NodeTimeout(f.Timeouts.PodStart), func(ctx context.Context) { scName := "mock-csi-storage-capacity-" + f.UniqueName m.init(ctx, testParameters{ registerDriver: true,