Timed tests generally stink - if you see a better way to represent the nature of that test, I'd be open to changes for sure. If you just want to bump the timeout, feel free to offer a pull request for review.
On Mon, Jun 26, 2017 at 8:54 PM, Andy Davidoff <[email protected]> wrote: > Running tests on a slow server demonstrated a false failure in > gremlin-driver’s ResultQueueTest.shouldDrainAsItemsArrive() due to an > insufficient delay of 3 seconds. In my case, I needed >10 seconds to > execute the test successfully. > > If this test is going to fail, having it take even 30 seconds to do so > doesn’t seem as important as having the test succeed when it should. I do > wonder if there isn’t a better way to write the test… > > -- > Andy Davidoff > disruptek.com > (877) DISRPTK > >
