Bump go 1.24.0

[Elbehery]

ref etcd-io/etcd#19417

cc @ivanvc @henrybear327

[ivanvc]

@Elbehery, please update the golangci-lint version to 1.64.5. As I mentioned it in etcd-io/raft#268 (comment)

[Elbehery]

@ivanvc raised #915

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahrtr, Elbehery

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

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

[Elbehery]

raised #916 to fix windows linter

[Elbehery]

/retest-required

[ivanvc]

@Elbehery, it looks like the tests are hanging and timing out in Prow. I noticed that the previous jobs were killed after 48 hours. Can you run them locally and check if they're not finishing? It's weird because they have a -timeout 30m argument 🤔

[Elbehery]

/retest

[Elbehery]

@Elbehery, it looks like the tests are hanging and timing out in Prow. I noticed that the previous jobs were killed after 48 hours. Can you run them locally and check if they're not finishing? It's weird because they have a -timeout 30m argument 🤔

@ivanvc I ran locally

make test

and it passes 👍🏽

I suggest to bump the timeout, because the freeList tests takes long time

wdyt @ahrtr about bumping the timeout ?

[Elbehery]

/retest

[Elbehery]

@ivanvc I don't know how to fix this 🤔

any suggestions ?

[ivanvc]

Increasing the timeout, I don't think, will make any difference, as it clearly is not terminating after the current set timeout.

I would start troubleshooting by debugging the script in the Prow infrastructure. You can add a set set -x in the Makefile or try to adjust the verbosity of the test execution. You can add a debug line at the end of the tests to see if it's hanging in the CI or on the side of the tests.

If you feel this is something beyond what you could do, we can reassign this version upgrade to me, and I'll take a look at it later.

[Elbehery]

Increasing the timeout, I don't think, will make any difference, as it clearly is not terminating after the current set timeout.
I would start troubleshooting by debugging the script in the Prow infrastructure. You can add a set set -x in the Makefile or try to adjust the verbosity of the test execution. You can add a debug line at the end of the tests to see if it's hanging in the CI or on the side of the tests.
If you feel this is something beyond what you could do, we can reassign this version upgrade to me, and I'll take a look at it later.

I will continue but mid week, hope it is fine 👍🏽

[ivanvc]

That sounds good. Can you draft the pull request to avoid generating the never-ending prow jobs? We can manually trigger the tests for draft pull requests. I'll also open a PR in test-infra to add a timeout to the jobs.