Fix UnlockEndpointIsDelayed again.
On DrMemory and Valgrind builds, it takes more than 1ms just to post the task inside UnlockEndpoint() and then enter the message loop, so the delayed task was being executed inside RunUntilIdle(). Remove the call to RunUntilIdle() and the check that the callback wasn't called inside it. The check at 314 is sufficient to verify that at least 1ms has passed, which in normal compiles means that a delay was applied. On DrMemory and Valgrind builds, the test may just verify that everything is running very slowly, but at least it will be deterministic. BUG=451999 TEST=net_unittests Review URL: https://codereview.chromium.org/878373002 Cr-Commit-Position: refs/heads/master@{#314093}
Showing
Please register or sign in to comment