Saga exceeded async timeout not helpful

[bdurrer]

The message Saga exceeded async timeout of 250ms indicates that there is an issue with a test. Somewhere, in the code base.

It should tell us what expectSaga triggered it or somehow give us the chance to find/debug it.

[pbylina]

Any news here? This message is very hard to debug.

[morzel85]

For those who are worried about the warnings: https://github.com/jfairbank/redux-saga-test-plan/blob/master/docs/integration-testing/timeout.md#silencing-warnings (most likely your code is just fine)

[bdurrer]

@morzel85 In our case the warning was almost always right, these often were test errors. But you have to count the warnings and compare to how many you expect to appear, because you don't know what and where it was caused

[AaronV]

I'm running into this too. It's very hard to figure out what timed out. In my case a spawn was being called, but I didn't really care and just need to add a new provider in the expectSaga.

But there are others in my project that I can't figure out. Each one ties up a thread in our test-runner for an extra 250ms, which can start to add up.