-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Disable the cache mutation detector. #9201
Disable the cache mutation detector. #9201
Conversation
`ENABLE_CACHE_MUTATION_DETECTOR` has been set for over a year, but due to a bug in the script parsing it, has not actually run. Fixing the bug such that it can run makes the tests time out. Since an hour is already a long time for presubmit tests, let's not make them longer and instead just stop enabling this. See kubernetes/kubernetes#67919 for more context.
/ok-to-test |
will this affect other ongoing PRs? |
In principle, this is a no-op for all PRs other than kubernetes/kubernetes#67919: the current configuration is such that this is effectively ignored due to the above bugs. In practice, I could be wrong, in which case this check does exist and would be disabled for all PRs. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Katharine, krzyzacy The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thanks! 👍 |
ENABLE_CACHE_MUTATION_DETECTOR
has been set for over a year. However, a week after it was set, a bug inconfigure-helper.sh
was introduced causing its value to be ignored. Fixing the bug such that it can run makes the tests time out. Since an hour is already a long time for presubmit tests, let's not make them even longer and instead just stop pretending that this works.Note that this will have no effect due to a another bug in the default configuration, which sets
ENABLE_CACHE_MUTATION_DETECTOR=false
, which is a non-empty string and will therefore cause it to be enabled anyway regardless of what is set here.Both of the above bugs are fixed in kubernetes/kubernetes#67919, but that cannot pass tests as long as this is enabled here due to the aforementioned timeouts.
(There is some degree of conjecture in this, since I do not know of a good way to run these tests with this flag changed other than by actually doing it.)