Fix golangci-lint timeout issue in CI

[seanmalloy]

Trying to pinpoint what is causing the golangci-lint timouts when running in CI.

/hold

[seanmalloy]

2 of 2 successful runs.

• Run 1: (no link)

level=info msg="Memory: 1774 samples, avg is 3396.9MB, max is 4070.3MB"
level=info msg="Execution took 3m16.835370238s"

• Run 2: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_descheduler/1574/pull-descheduler-verify-master/1867335653298016256

level=info msg="Memory: 609 samples, avg is 1882.0MB, max is 3888.8MB"
level=info msg="Execution took 1m17.730608964s"

• Run 3: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_descheduler/1574/pull-descheduler-verify-master/1867338050514718720

level=info msg="Memory: 607 samples, avg is 1898.0MB, max is 3980.1MB"
level=info msg="Execution took 1m18.31162079s"

[seanmalloy]

/test pull-descheduler-verify-master

[seanmalloy]

/test pull-descheduler-verify-master

[a7i]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: a7i

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 [a7i]

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

[a7i]

@seanmalloy fyi, here is the resource utilization:

https://monitoring-eks.prow.k8s.io/d/96Q8oOOZk/builds?var-org=kubernetes-sigs&var-repo=descheduler&var-job=pull-descheduler-verify-master&orgId=1&from=1734041463549&to=1734045104101

it looks to be a resource issue but it's already pretty high: https://github.com/a7i/test-infra/blob/master/config/jobs/kubernetes-sigs/descheduler/descheduler-presubmits-master.yaml#L53-L57

[seanmalloy]

/test pull-descheduler-verify-master

[seanmalloy]

Updates since merging kubernetes/test-infra#33946. It looks like we might be good now after bumping CPU to 8 and Memory to 8 GBi

10 of 10 runs successful.

• Run 1

level=info msg="Memory: 467 samples, avg is 2106.0MB, max is 4766.7MB"
level=info msg="Execution took 59.135479519s"

• Run 2

level=info msg="Memory: 502 samples, avg is 2110.4MB, max is 4781.9MB"
level=info msg="Execution took 1m0.066928051s"

• Run 3

level=info msg="Memory: 453 samples, avg is 1969.9MB, max is 4467.3MB"
level=info msg="Execution took 58.908604213s"

• Run 4

level=info msg="Memory: 464 samples, avg is 2096.0MB, max is 4552.1MB"
level=info msg="Execution took 58.62517406s"

• Run 5

level=info msg="Memory: 502 samples, avg is 1941.8MB, max is 3946.4MB"
level=info msg="Execution took 1m1.485046295s"

• Run 6

level=info msg="Memory: 471 samples, avg is 1983.0MB, max is 4115.5MB"
level=info msg="Execution took 1m0.903941678s"

• Run 7

level=info msg="Memory: 507 samples, avg is 1946.7MB, max is 4016.3MB"
level=info msg="Execution took 59.137035231s"

• Run 8

evel=info msg="Memory: 502 samples, avg is 2084.3MB, max is 4759.1MB"
level=info msg="Execution took 1m1.973715188s"

• Run 9

level=info msg="Memory: 515 samples, avg is 1959.0MB, max is 4236.8MB"
level=info msg="Execution took 1m2.449222029s"

• Run 10

level=info msg="Memory: 518 samples, avg is 1952.9MB, max is 3913.6MB"
level=info msg="Execution took 1m3.571413578s"

I'll run the pull-descheduler-verify-master CI job against this PR a few more times to make sure we are all good and then close this PR.

[seanmalloy]

/test pull-descheduler-verify-master

[a7i]

Looks like I did not need to increase memory, but it used up whatever CPU we gave it

https://monitoring-eks.prow.k8s.io/d/96Q8oOOZk/builds?var-org=kubernetes-sigs&var-repo=descheduler&var-job=pull-descheduler-verify-master&orgId=1&from=1734108578016&to=1734109629074

[seanmalloy]

/test pull-descheduler-verify-master

[k8s-ci-robot]

@seanmalloy: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-descheduler-test-e2e-k8s-master-1-31	bd023b8	link	true	/test pull-descheduler-test-e2e-k8s-master-1-31

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[seanmalloy]

/test pull-descheduler-verify-master

[seanmalloy]

/test pull-descheduler-verify-master

[seanmalloy]

/test pull-descheduler-verify-master

[seanmalloy]

/test pull-descheduler-verify-master

[seanmalloy]

/test pull-descheduler-verify-master

[seanmalloy]

/test pull-descheduler-verify-master

[seanmalloy]

/test pull-descheduler-verify-master

[seanmalloy]

/test pull-descheduler-verify-master

[seanmalloy]

Bumping CPU and Memory seems to have fixed the issue with the pull-descheduler-verify-master CI job randomly failing. See #1574 (comment) for a detailed summary.

References:

• update descheduler-presubmits-master to allocate more resources kubernetes/test-infra#33946
• Bump CPU and Memory Resources For All pull-descheduler-verify Jobs kubernetes/test-infra#33951

/close

[k8s-ci-robot]

@seanmalloy: Closed this PR.

In response to this:

Bump CPU and Memory seems to have fixed the issue with the pull-descheduler-verify-master CI job randomly failing. See #1574 (comment) for a detailed summary.

References:

• update descheduler-presubmits-master to allocate more resources kubernetes/test-infra#33946
• Bump CPU and Memory Resources For All pull-descheduler-verify Jobs kubernetes/test-infra#33951

/close

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.