-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Clarify the invalidation of REPO_CONTENTS_CACHE_DIRS FileStateValues #28222
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
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.
Code Review
This pull request introduces several valuable improvements. It clarifies the invalidation logic for REPO_CONTENTS_CACHE_DIRS by making an implicit assumption explicit with a fail-fast exception. It also fixes a crash when an invalid repository rule is referenced by a target, and adds a new test to cover this scenario. Furthermore, the test coverage for the repository contents cache is significantly improved by verifying file contents, not just caching behavior. Finally, the update to the test infrastructure to provide real-time process output is a great quality-of-life improvement for developers. The changes are well-structured and look good.
Along the way, improve the test coverage for repo contents cache deletion by asserting that non-BUILD files within it actually exist on disk rather than just exist from the point of Skyframe. Also fix a crash observed while working on the test improvements.
|
@bazel-io fork 9.0.0 |
Since this behavior is quite surprising (it definitely was to the author), this change also improves the test coverage for repo contents cache deletion by asserting that non-BUILD files within it actually exist on disk rather than just exist from the point of Skyframe.
Also fix a crash observed while working on the test improvements.