increase ginkgo timeout for serial jobs on kubetest2

[elieser1101]

Serial jobs seem to be timing out https://storage.googleapis.com/kubernetes-ci-logs/pr-logs/pull/128092/pull-kubernetes-node-kubelet-serial-crio-cgroupv1-kubetest2/1847639771518603264/artifacts/build-log.txt
this should fix it.

part of #32567

[k8s-ci-robot]

Hi @elieser1101. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[aojea]

/hold

please let's try to be more rigorous with these kind of changes

the log you link indicates a timeout ... from one specific test, not of the job

Summarizing 1 Failure:
  [TIMEDOUT] [sig-node] Device Plugin [NodeFeature:DevicePlugin] [Serial] DevicePlugin [Serial] [Disruptive] [AfterEach] Can schedule a pod with a restartable init container [NodeFeature:SidecarContainers] [sig-node, NodeFeature:DevicePlugin, Serial, Disruptive, NodeFeature:SidecarContainers]
  k8s.io/kubernetes/test/e2e_node/device_plugin_test.go:198

Ran 22 of 667 Specs in 1801.678 seconds
FAIL! - Suite Timeout Elapsed -- 21 Passed | 1 Failed | 0 Pending | 645 Skipped
--- FAIL: TestE2eNode (1801.71s)
FAIL

Ginkgo ran 1 suite in 30m1.856789007s

The job runs in 30 minutes

[kannon92]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elieser1101, kannon92

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:

• config/jobs/kubernetes/sig-node/OWNERS [kannon92]

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

[kannon92]

@aojea the non kubetest job takes about 3 hours. This finishing in 30 minutes is a bug from converting to kubetest2.

[aojea]

@aojea the non kubetest job takes about 3 hours. This finishing in 30 minutes is a bug from converting to kubetest2.

independently, it runs now in 30 minutes, changing the timeout will not make any difference, the job will still be running in 30 minutes

anyway, I let you handle this since migrations require a lot of try and error

/hold cancel

[k8s-ci-robot]

@elieser1101: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key sig-node-presubmit.yaml using file config/jobs/kubernetes/sig-node/sig-node-presubmit.yaml

In response to this:

Serial jobs seem to be timing out https://storage.googleapis.com/kubernetes-ci-logs/pr-logs/pull/128092/pull-kubernetes-node-kubelet-serial-crio-cgroupv1-kubetest2/1847639771518603264/artifacts/build-log.txt
this should fix it.

part of #32567

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-sigs/prow repository.