DiscoveryClientServiceInstanceListSupplierTests.shouldReturnEmptyInstancesListOnTimeoutBlockingClient() fails

[spencergibb]

The test should return nothing after the timeout, but the test is returning an instance. I suspect this has to do with how we are testing.

[OlgaMaciaszek]

There seems to be a behaviour change with the .timeout() method rather than a test issue. Have tried testing with a version of a DiscoveryClient that actually delays the response, as opposed to the mock, and in debug with Reactor 3.3.8.RELEASE, we do not enter this line, while with Reactor 3.3.7.RELEASE it does, i.e., it looks that with the new version, the timeout() method does not get executed. I see this release has, indeed, included changes related to timeouts. Will contact Reactor team.