-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CI] ARM CNCF workers starvation #32447
Comments
To start with, we will limit the Go version that we run on for CI testing. We will only run on 1.22 for ARM. |
**Description:** Exclude running tests on Go 1.21 with ARM CI. **Link to tracking Issue:** #32447
Potentially related: #32445 |
OK, the fix is in place, I'll circle back once we have more data on how much this helps with pressure. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
I think we can close this issue, we have moved the ARM build to a separate workflow and this is no longer seen as an issue. I could not access stats to verify. |
Component(s)
No response
Describe the issue you're reporting
We are now running on ARM CI workers, and our build is taxing the infrastructure.
It looks like we push too many jobs on the infra, and therefore starve other projects from accessing workers.
This issue tracks efforts to reduce our usage of CI resources.
The text was updated successfully, but these errors were encountered: