RFR: 8286873: Improve websocket test execution time [v2]

Pavel Rappo prappo at openjdk.java.net
Thu May 19 10:49:43 UTC 2022


On Thu, 19 May 2022 09:42:05 GMT, Daniel Jeliński <djelinski at openjdk.org> wrote:

> > What looks questionable is rearrangement of asserts: when `assertHangs` moves down. assertNotDone(cfClose) can transitorry pass even if ping has not hung.
> 
> `assertHangs` either waits for 5 seconds or throws an exception, so `assertNotDone` after `assertHangs` is pretty much equivalent to `assertHangs`

The order of these checks is important. On the other hand, I'm not sure how important that importance is for the tests. With the proposed change, the test might become more permissive than it should've been.

Separately, why does this PR change `assertHangs(cfClose)` to `assertNotDone(cfClose)`?

The fact that you say that the tests still pass gives me some confidence. I'm just trying to make sure that the tests still test what we think they test.

-------------

PR: https://git.openjdk.java.net/jdk/pull/8746


More information about the net-dev mailing list