Event Stream Caching and Fuzziness

We use events as barriers/synchronization primitives in test, but like all the time, we're fighting a losing battle against race conditions.  Consider per test shared informers, that retain history, allow notification, even fuzzy matching of events (e.g. it happened 3 seconds ago, but that's fine as we're aware of a race condition).