unit tests failing about justsaying HOT 4 CLOSED

Integration tests are flaky due to lack of loopback/in-memory transport. The timing issue exist as long as we use real aws topics/queues for tests. There's been several half attempts to address this but none that can be introduced without a major redesign. Ideas/PRs are welcome.

from justsaying.

when I was working on the PR for making the SQS receive loop async I noticed that some of the timing-sensitive tests (not only the integration cases) that fail from time to time seem to be related to the way you wait synchronously (by putting the current thread to sleep), which can impact the execution of handler code.

In the async version this became more noticeable because all async callbacks are executed against the ThreadPool (which unless otherwise specified, starts with 1 thread) so if that thread is being blocked by the observation code (say, Patiently.VerifyExpectation) then the async callbacks won't get a chance to execute (until additional threads are made available and it gets a slot to run, how and when this happens is a runtime decision the ThreadPool makes based on its hill-climbing algo and based on my observation makes a few of the tests fail about 4/5 times).

from justsaying.

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from justsaying.

Closed automatically due to inactivity.

from justsaying.