You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
TST: Investigate cache warnings in tests (currently ignored) #9620
Running with -Werror should clarify - in a few cases I explicitly run tests where the cache is badly misconfigured, and in these cases we should demand emission of this warning (a warning because the code should fall back to no cache, but the user should know the cache isn't working). In other cases it may be being emitted when the cache is simply missing, and these are bugs.
If the problem arises only on Windows, it may be possible to trigger it on other systems by using the context manager to enforce use of the "dumb" dbm backend; this may not work, as Windows sometimes produces different exceptions in problematic filesystem conditions.
Activity
aarchiba commentedon Nov 19, 2019
Running with -Werror should clarify - in a few cases I explicitly run tests where the cache is badly misconfigured, and in these cases we should demand emission of this warning (a warning because the code should fall back to no cache, but the user should know the cache isn't working). In other cases it may be being emitted when the cache is simply missing, and these are bugs.
If the problem arises only on Windows, it may be possible to trigger it on other systems by using the context manager to enforce use of the "dumb" dbm backend; this may not work, as Windows sometimes produces different exceptions in problematic filesystem conditions.