Memory spike while building 1.29 binaries crashes staging runs

[puerco]

What happened:

When running builds in parallel, memory consumption jumps around the time go-runner is being built. This causes the staging process to exit as memory is exhausted.

What you expected to happen:

Builds should finish successfully

How to reproduce it (as minimally and precisely as possible):

Run a staging run of the release-1.29 branch. Or those with access can check out run c56008f6 in the GCB console.

Anything else we need to know?:

We mitigated the crashing stage run by switching to serial builds. This is a temporary measure, however as it causes the builds to run slower.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[xmudrii]

1.29 is EOL, but the mitigation is still in place, we should investigate if it's still needed
/remove-lifecycle stale