-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Disallow output bases under GC-able directories #26138
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
base: master
Are you sure you want to change the base?
Conversation
We have had user's report spurious build failures due to the disk cache GC collecting files under the output base when output base and disk cache were set up at the same path.
We might need something more elaborate here as repo contents and disk cache probably also shouldn't share a directory. Maybe BlazeModules should report their managed directories? |
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.
The error messages don't match the condition we're testing for.
To be clear: a cache inside the output base should be ok (though perhaps ill-advised), only the output base inside a cache is a problem?
Separately - should we canonicalize paths so that the check isn't defeated by a symlink?
Canonicalizing paths requires more care as symlinks may not exist, will mark as ready for review again when that is fixed. |
58d31c5
to
5a8197e
Compare
CI is green now. I also added comments on why intermediate symlinks don't need to be checked. |
We have had user's report spurious build failures due to the disk cache GC collecting files under the output base when output base and disk cache were set up at the same path.