generator: Drop build frequencies#923
Merged
nathanchance merged 2 commits intoMar 21, 2026
Merged
Conversation
In order to reduce the amount of resources needed to run the matrix, reduce how frequently certain builds run. For mainline, doing builds frequently during the -rc period after the merge window is somewhat wasteful, as the changes going in at that point should be low risk for build regressions. For -next, catching breakage with older toolchains is important but it is not worth running builds every day for. Lastly, reduce some of the stable and android-mainline build frequencies since their source is not changing super frequently either (and most regressions should come from mainline or LLVM, which continues to have frequent coverage). This saves about 3500 builds per week. Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Member
|
Ack thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In order to reduce the amount of resources needed to run the matrix, reduce how frequently certain builds run.
For mainline, doing builds frequently during the -rc period after the merge window is somewhat wasteful, as the changes going in at that point should be low risk for build regressions.
For -next, catching breakage with older toolchains is important but it is not worth running builds every day for.
Lastly, reduce some of the stable and android-mainline build frequencies since their source is not changing super frequently either (and most regressions should come from mainline or LLVM, which continues to have frequent coverage).
This saves about 3500 builds per week.