There is quite a lot of fail in the unit tests, and a bit in the production code too.
Many of the unit tests are using the timeout defaults that we use in the production code. A couple of years ago we had changed the tests to use test-specific timeouts because I/O timeouts happen in CI, but apparently that got lost somewhere along the way.
The production code has an issue also: the "state.State.ForModel" method dials with the default mongo dial options rather than with the same options you used to open state in the first place.
I'll put some test-specifics in a central spot and make sure we're using them everywhere.
There is quite a lot of fail in the unit tests, and a bit in the production code too.
Many of the unit tests are using the timeout defaults that we use in the production code. A couple of years ago we had changed the tests to use test-specific timeouts because I/O timeouts happen in CI, but apparently that got lost somewhere along the way.
The production code has an issue also: the "state. State.ForModel" method dials with the default mongo dial options rather than with the same options you used to open state in the first place.
I'll put some test-specifics in a central spot and make sure we're using them everywhere.