🌱 test/e2e: increase Ginkgo poll progress after to 1h

[sbueringer]

Signed-off-by: Stefan Büringer [email protected]

What this PR does / why we need it:
Currently we get a progress report after 10m every 1m. Unfortunately it's not that useful as it just prints the current stack (e.g. https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api/7871/pull-cluster-api-e2e-full-release-1-3/1612472872549224448/build-log.txt)

Let's increase the timeout so we only get the report if something is stuck for >= 1h.

xref: https://kubernetes.slack.com/archives/C8TSNPY4T/p1673336168049309

Cherry-picking to other supported branches to make e2e test debugging easier there as well.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[sbueringer]

cc @fabriziopandini @oscr

[sbueringer]

/cherry-pick release-1.3

[k8s-infra-cherrypick-robot]

@sbueringer: once the present PR merges, I will cherry-pick it on top of release-1.3 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.3

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sbueringer]

/cherry-pick release-1.2

[k8s-infra-cherrypick-robot]

@sbueringer: once the present PR merges, I will cherry-pick it on top of release-1.2 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[killianmuldoon]

/lgtm

Seems reasonable to me

[oscr]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 7e3b9345cb4c9a23c04ed2c5022d56dca2da54da

[oscr]

/lgtm

[sbueringer]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sbueringer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sbueringer]

/retest

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #7891

In response to this:

/cherry-pick release-1.3

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-infra-cherrypick-robot]

@sbueringer: #7888 failed to apply on top of branch "release-1.2":

Applying: test/e2e: increase Ginkgo poll progress after to 1h
Using index info to reconstruct a base tree...
M	Makefile
Falling back to patching base and 3-way merge...
Auto-merging Makefile
CONFLICT (content): Merge conflict in Makefile
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 test/e2e: increase Ginkgo poll progress after to 1h
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sbueringer]

Doesn't exist on release-1.2 so we don't need a cherry-pick for that branch.