Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Memory spike while building 1.29 binaries crashes staging runs #3837

Open
puerco opened this issue Nov 21, 2024 · 0 comments
Open

Memory spike while building 1.29 binaries crashes staging runs #3837

puerco opened this issue Nov 21, 2024 · 0 comments
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/bug Categorizes issue or PR as related to a bug. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@puerco
Copy link
Member

puerco commented Nov 21, 2024

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.

@puerco puerco added kind/bug Categorizes issue or PR as related to a bug. sig/release Categorizes an issue or PR as relevant to SIG Release. area/release-eng Issues or PRs related to the Release Engineering subproject labels Nov 21, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/bug Categorizes issue or PR as related to a bug. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

No branches or pull requests

2 participants