test: increase timeout for test-tls-fast-writing

[Trott]

Increase timeout for test from 500ms to 5000ms so busy slow machines
don't produce false positives.

Fixes: #4964

[silverwind]

Factor 10 seems a bit much, no? Do CI machines do multiple runs in parallel?

[Trott]

@silverwind asked:

Factor 10 seems a bit much, no?

There's no real advantage to "right-sizing" the timeout other than a user waits a second or two less on a failed test at the command line. So I'd rather put in a preposterous increase now and never have to deal with the problem again instead of putting in a modest increase now and needing to put in another modest increase or two in a month.

Do CI machines do multiple runs in parallel?

I don't think they do yet but I believe @jbergstroem is not far from having that implemented. (Or was the switch already flipped on that?)

[jbergstroem]

@Trott still not implemented.

[Trott]

@silverwind If reducing the increase from a factor of 10 to a factor of (say) 2 would make you more comfortable with the change, I'm totally OK with doing that instead.

[silverwind]

My issue is that these tests usually set a performance goal through these timeouts, I think I'd be okay with something more modest like 2x or 3x.

[Trott]

@silverwind OK, changed to 1000ms instead of 5000ms.

CI: https://ci.nodejs.org/job/node-test-pull-request/1783/

[Trott]

CI is green except for one host that failed to finish building. Looks good to anyone? @nodejs/testing

[orangemocha]

LGTM

[Trott]

Landed in c133d07