The ldap_user_cache_refresher.js test has seen sporadic failures for quite some time now. Since this test uses a locally-running mock server, these failures cannot be explained by external LDAP server slowness. The test currently enforces that it must see cache invalidations within a configurable ldapUserCacheStalenessInterval seconds after the last successful refresh. This sometimes fails because in the worst case scenario, a failed refresh completes at just under ldapUserCacheStalenessInterval seconds. As a result, the server waits another ldapUserCacheRefreshInterval seconds before trying another refresh and only invalidates the cache if that refresh also fails.

To temporarily fix this and make the build green, we should relax this interval to be ldapUserCacheStalenessInterval + ldapUserCacheRefreshInterval. Eventually, we should update the behavior of the cache so that it actually performs the invalidation when the ldapUserCacheStalenessInterval is reached.