flaky: parallel/test-https-foafssl

[refack]

• Version: master
• Platform: Windows 10
• Subsystem: openssl

• test file - parallel/test-https-foafssl
• ci job - binary-windows/21613/COMPILED_BY=vs2017,RUNNER=win10
• ci worker - test-azure_msft-win10-x64-2
• output:

  11:00:21 not ok 298 parallel/test-https-foafssl
  11:00:21   ---
  11:00:21   duration_ms: 120.155
  11:00:21   severity: fail
  11:00:21   exitcode: 1
  11:00:21   stack: |-
  11:00:21     timeout
  11:00:21     got request
  11:00:21   ...
  

/CC @nodejs/platform-windows @nodejs/crypto

[refack]

/CC @nodejs/http

[Trott]

Can't reproduce locally. Let's try CI stress test:

https://ci.nodejs.org/job/node-stress-single-test/2093/

RUN_TEST: -J --repeat 10 parallel/test-https-foafssl
RUN_TIMES: 100
RUN_LABEL: win10-1p-vs2015 and win10-vs2017

Both hosts are Azure hosts in that stress test run, just like in the only reported failure above.

[refack]

vs2015 is not supported for node > 8.
But I added the server flavor equivalent of windows 10 - Windows2016 single processor.
https://ci.nodejs.org/job/node-stress-single-test/2094/nodes=win2016-1p-vs2017/
https://ci.nodejs.org/job/node-stress-single-test/2​10​0/nodes=win2016-1p-vs2017/

[EDIT by @Trott] https://ci.nodejs.org/job/node-stress-single-test/2100/nodes=win2016-1p-vs2017/

[Trott]

Relevant stress tests are green.
¯\(ツ)/¯

[Trott]

It's back.

https://ci.nodejs.org/job/node-test-binary-windows-js-suites/5131/RUN_SUBSET=2,nodes=win10-COMPILED_BY-vs2019/console

test-azure_msft-win10_vcbt2015-x64-4

00:19:56 not ok 743 parallel/test-https-foafssl
00:19:56   ---
00:19:56   duration_ms: 120.185
00:19:56   severity: fail
00:19:56   exitcode: 1
00:19:56   stack: |-
00:19:56     timeout
00:19:56     got request
00:19:56   ...