Fix UnlockEndpointIsDelayed again.

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

Committed: https://crrev.com/ba6836202b8d60478d96fd8509ad98cd89e1ee1c
Cr-Commit-Position: refs/heads/master@{#314093}

[Adam Rice, 2015-01-28 07:09:38]

ricea@chromium.org changed reviewers:
+ tyoshino@chromium.org

[Adam Rice, 2015-01-28 09:01:22]

ricea@chromium.org changed reviewers:
+ mmenke@chromium.org

[Adam Rice, 2015-01-28 09:01:22]

+mmenke for net/ OWNERS.

[Adam Rice, 2015-01-28 09:10:00]

On 2015/01/28 09:01:22, Adam Rice wrote:
> +mmenke for net/ OWNERS.

Oh, sorry, tyoshino hasn't reviewed it yet. I got my CLs mixed up.

mmenke, if it is okay with you please wait for tyoshino's review.

[tyoshino (SeeGerritForStatus), 2015-01-29 09:12:19]

lgtm

[mmenke, 2015-01-30 15:26:16]

LGTM, rubberstamp (Sorry for not getting to this earlier, took a couple days off
during and after the blizzard)

[Adam Rice, 2015-02-01 17:18:53]

The CQ bit was checked by ricea@chromium.org

[commit-bot: I haz the power, 2015-02-01 17:19:22]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/878373002/1

[commit-bot: I haz the power, 2015-02-01 18:17:23]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-01 18:18:26]

Patchset 1 (id:??) landed as
https://crrev.com/ba6836202b8d60478d96fd8509ad98cd89e1ee1c
Cr-Commit-Position: refs/heads/master@{#314093}