-
Notifications
You must be signed in to change notification settings - Fork 510
Open
Labels
area/release-engIssues or PRs related to the Release Engineering subprojectIssues or PRs related to the Release Engineering subprojectkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.needs-prioritysig/releaseCategorizes an issue or PR as relevant to SIG Release.Categorizes an issue or PR as relevant to SIG Release.
Description
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.
Metadata
Metadata
Assignees
Labels
area/release-engIssues or PRs related to the Release Engineering subprojectIssues or PRs related to the Release Engineering subprojectkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.needs-prioritysig/releaseCategorizes an issue or PR as relevant to SIG Release.Categorizes an issue or PR as relevant to SIG Release.