Prow update master

[avorima]

/kind cleanup

Update release-tools according to kubernetes-csi/csi-release-tools#7

Squashed 'release-tools/' changes from 227577e0..734c2b95

734c2b95 Merge pull request #265 from Rakshith-R/consider-main-branch
f95c855b Merge pull request #262 from huww98/golang-toolchain
3c8d966f Treat main branch as equivalent to master branch
e31de525 Merge pull request #261 from huww98/golang
fd153a9e Bump golang to 1.23.1
a8b3d050 pull-test.sh: fix "git subtree pull" errors
6b05f0fc use new GOTOOLCHAIN env to manage go version

git-subtree-dir: release-tools
git-subtree-split: 734c2b950c4b31f64b63052c64ffa5929d1c9b97

NONE

[k8s-ci-robot]

Hi @avorima. Thanks for your PR.

I'm waiting for a kubernetes-csi 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.

[jsafrane]

/ok-to-test

[TerryHowe]

Ideally would contain kubernetes-csi/csi-release-tools#259

[avorima]

@jsafrane i see this pull-kubernetes-csi-external-attacher-1-29-on-kubernetes-1-29 job fail on some other similar pull requests too. seemingly with the same error message: flag provided but not defined: -ginkgo.parallel.node.
i couldn't find where this flag is set, but the ginkgo version that is installed is very outdated: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-csi_external-attacher/606/pull-kubernetes-csi-external-attacher-1-29-on-kubernetes-1-29/1866138821075144704#1:build-log.txt%3A548
do you know how we could proceed here?

[jsafrane]

do you know how we could proceed here?

I don't. Someone needs to dive into the scripts used to run the tests and where they come from and why they don't work. I don't have much "secret" knowledge here.

[avorima]

/retest-required

[jsafrane]

Thanks for the PR!
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: avorima, jsafrane

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:

• release-tools/OWNERS [jsafrane]

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

[jsafrane]

I can see kubernetes-csi/csi-release-tools#267 helped