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.
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
extend the "if-unchanged" logic for compiler builds #131831
extend the "if-unchanged" logic for compiler builds #131831
Changes from 3 commits
baa95ef
72e63e3
a00fd7a
6b38a15
bc75310
4dfc052
2d143ab
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a bunch of miscellaneous stuff in
src/etc
. Are you 100% confident none of it affects the build?As others said before me, the attitude here should be to start with an empty list, and only add things where we are fully confident they are fine to add, and adding them is worth it in terms of caching.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, it’s too risky to include that and definitely not worth caching.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So which ones are worth caching?
tests
,src/tools
-- anything else?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which one doesn’t seem obviously safe to cache from the current list? Because even if they are rarely merged alone with bors, they will still be very useful in PR CI (by cutting one of the runner’s times in half).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As several people said above, that is the wrong question. You had several items in your list that turned out to be potentially problematic. Clearly you considered them "obviously safe", and they weren't.
So unless there's some obvious benefit to including a directory -- like, we regularly have PRs that change only those files -- it should not be included.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I never considered them "obviously safe". I wasn’t sure about them and was hoping to get some help from the reviews.
But sure, I can reduce the list even more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
build_helper
is a dependency of bootstrap, but excluded here, which seems wrong.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's no longer part of
src/tools
.