As per #1582 we technically should not need to retry our route state in E2E tests and wait for a success any more. In fact, the RetryingRouteInconsistency helper has been dumbed down to be a noop at this point.
However, currently this function provides a neat singular piece of code that can be patched downstream to still retry the relevant bits, without diluting tests too much.
I'd be forever greatful if we could hold off cleanup until at least this patch need is resolved and leaving breadcrumbs as to why it's still there here.
As per #1582 we technically should not need to retry our route state in E2E tests and wait for a success any more. In fact, the
RetryingRouteInconsistencyhelper has been dumbed down to be a noop at this point.However, currently this function provides a neat singular piece of code that can be patched downstream to still retry the relevant bits, without diluting tests too much.
I'd be forever greatful if we could hold off cleanup until at least this patch need is resolved and leaving breadcrumbs as to why it's still there here.