There is a concurrency issue in the test, which lets the test advance too fast, assuming that the new addresses have already been "stored" by the CacheInvalidationSender. This change adds a new "probe" that is triggered after the (new) addresses have been "stored".
There is a concurrency issue in the test, which lets the test advance too fast, assuming that the new addresses have already been "stored" by the
CacheInvalidationSender. This change adds a new "probe" that is triggered after the (new) addresses have been "stored".