Give asan/win bot a very generous timeout.

Give asan/win bot a very generous timeout.

The previous increase in r293993 didn't help anything; make the timeout really
large to make sure that things aren't just slow. (Once this hasn't helped
either, we're going to remove this win/asan special case.)

BUG=412471
TBR=timurrrr@chromium.org
NOTRY=true

Committed: https://crrev.com/207907c24b8cee246ff713342a1055277b64355d
Cr-Commit-Position: refs/heads/master@{#294242}

[Nico, 2014-09-10 21:54:20]

The CQ bit was checked by thakis@chromium.org

[commit-bot: I haz the power, 2014-09-10 22:02:21]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/thakis@chromium.org/557333007/1

[commit-bot: I haz the power, 2014-09-10 22:15:33]

Committed patchset #1 (id:1) as 3ce99a8871aa04557e7faf76d87b905f3fdce517

[commit-bot: I haz the power, 2014-09-10 22:26:27]

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

[Timur Iskhodzhanov, 2014-09-11 13:54:07]

LGTM, though it didn't help :(

[Timur Iskhodzhanov, 2015-01-15 18:10:22]

As per crbug.com/412471 this was not related to timeouts, maybe it's time to
revert this change?  Any objections?
[3x sounds OK, 8x is indeed too generous]

[Nico, 2015-01-15 18:14:58]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/828403005/ by thakis@chromium.org.

The reason for reverting is: Didn't help, wasn't the cause (see bug)..