-
Notifications
You must be signed in to change notification settings - Fork 8
test stable less with released versions of clang #200
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
Comments
The cron schedule is currently tied to a tree in |
For trees that do not move as frequently, such as stable and the Android trees, there is little point to testing every day with versions of clang that cannot be patched. To help load balance, build the stable trees on Wednesday and the Android trees on Sunday. Closes: ClangBuiltLinux#200 Signed-off-by: Nathan Chancellor <[email protected]>
I have a proof of concept at https://github.com/nathanchance/continuous-integration2/commits/cron-schedule-logic-shuffle. |
For trees that do not move as frequently, such as stable and the Android trees, there is little point to testing every day with versions of clang that cannot be patched. To help load balance, build the stable trees on Wednesday and the Android trees on Sunday. Closes: ClangBuiltLinux#200 Signed-off-by: Nathan Chancellor <[email protected]>
For trees that do not move as frequently, such as stable and the Android trees, there is little point to testing every day with versions of clang that are EOL, since they are not being updated anymore. To help load balance, build the stable trees on Wednesday and the Android trees on Sunday. Closes: ClangBuiltLinux#200 Signed-off-by: Nathan Chancellor <[email protected]>
@nathanchance mentioned in the CBLII meetup that we test stable daily, though it's generally updated weekly, because we want to catch LLVM regressions ASAP. If we're testing clang-12 though which isn't going to see updates, we can scale back the frequency of those tests I suspect.
The text was updated successfully, but these errors were encountered: