flaky test: goroutine leak about river

[brandur]

Ugh, these are always fun.

Given that it looks like the goroutines are coming from an elected queue maintainer, I kinda suspect there might be some race in the client wherein a call to Stop doesn't guarantee a maintainer isn't still able to succeed in an election simultaneously and ignore it. (Or at least for some amount of time.)

[brandur]

This is another that I suspect may have gotten fixed up along the way (don't remember fixing this exactly, but fixed some very like it in some service refactors), and which I haven't seen in a very long time and hundreds of test runs. Going to optimistically close it for now, but reopen if you happen to catch it again.