Skip to content

Commit

Permalink
e2e: apply timeout for CSI Storage Capacity test only to node
Browse files Browse the repository at this point in the history
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.
  • Loading branch information
pohly authored and aojea committed May 26, 2023
1 parent 916bc55 commit f41a169
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion test/e2e/storage/csi_mock/csi_storage_capacity.go
Original file line number Diff line number Diff line change
Expand Up @@ -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,
Expand Down

0 comments on commit f41a169

Please sign in to comment.