Flaky http2-settings-flood

[BridgeAR]

Multiple timeouts on this test:

https://ci.nodejs.org/job/node-test-commit-freebsd/14756/nodes=freebsd10-64/console
https://ci.nodejs.org/job/node-test-commit-freebsd/14746/nodes=freebsd10-64/console

not ok 2035 sequential/test-http2-settings-flood
  ---
  duration_ms: 120.105
  severity: fail
  stack: |-
    timeout

[jasnell]

hmm... yeah, it's a limitation on the ability of the test to trigger the actual error condition being tested for. Basically, in most cases the test actually should fail because the failure condition is supposed to be avoided by the nature of the how the code is implemented. The test is attempting to test an edge case that is inherently flaky and very operating system dependent. We have the same issue with http2-ping-flood. I've been trying to come up with a more reliable alternative approach but haven't been able to find one.

[Trott]

Definitely happens on Windows too, more frequently than FreeBSD. (It's marked flaky on Windows.)

https://ci.nodejs.org/job/node-test-binary-windows/15672/COMPILED_BY=vs2017,RUNNER=win10,RUN_SUBSET=1/console

not ok 529 sequential/test-http2-settings-flood # TODO : Fix flaky test
  ---
  duration_ms: 120.185
  severity: fail
  stack: |-
    timeout

[Trott]

Hopeful fix. We'll see. #19349