We were getting flushes in an unexpected order while running tests because our connectivity monitor was running, delaying requests until it detected a connection. This delay was compounded by the flush timer, which could fire other flush events during this delay. Disable them both for EventPipeline tests.
Additionally, wait for a connection response vs just firing off a request in the simultaneous connection test to ensure it is completed before we attempt to clean up.
Checklist
[X] Does your PR title have the correct title format?
Summary
We were getting flushes in an unexpected order while running tests because our connectivity monitor was running, delaying requests until it detected a connection. This delay was compounded by the flush timer, which could fire other flush events during this delay. Disable them both for EventPipeline tests.
Additionally, wait for a connection response vs just firing off a request in the simultaneous connection test to ensure it is completed before we attempt to clean up.
Checklist