[v8.x] flaky sequential/test-http2-settings-flood

[mcollina]

In a recent CI run there was a crash sequential/test-http2-settings-flood

13:27:16 not ok 528 sequential/test-http2-settings-flood
13:27:16   ---
13:27:16   duration_ms: 1.37
13:27:16   severity: crashed
13:27:16   exitcode: -1073741819
13:27:16   stack: |-

• Version: master
• Platform: Windows
• Subsystem: http2

[mcollina]

cc @jasnell

[mcollina]

Prior art: #18251 #19349.

[mcollina]

cc @Trott

[Trott]

Link to the CI run would be very useful. In particular, I think this was a CI run on the v8.x branch, was it not? It might be a bug that's already been fixed in master.

[Trott]

Oh, wait, you wrote "master" above. Yeah, link would be good. Would want to know what Windows variant etc.

[Trott]

Argh! http2. Yeah, that has to be master, not v8.x. I read it as https for some reason. Sorry for all the noise...

[Trott]

Found one...

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

test-azure_msft-win10-x64-4

09:53:40 not ok 529 sequential/test-http2-settings-flood
09:53:40   ---
09:53:40   duration_ms: 1.139
09:53:40   severity: crashed
09:53:40   exitcode: -1073741819
09:53:40   stack: |-
09:53:40   ...

Timestamps are different than the console cut-and-paset from @mcollina so this has happened at least twice. Probably a good idea to mark it flaky until it gets worked out. One bugfix is probably going to resolve a ton of these flaky tests all at once.

[Trott]

Argh! It IS v8.x after all! Yeah, this is probably not affecting master.

(Why did I think http2 didn't exist in v8.x?)

[MylesBorins]

marked flaky on 8.x in 2bedbdb

[BridgeAR]

Node.js v8.x has reached the end-of-life and won't receive any fixes anymore. I am closing this since this issue only applies to Node.js v8.x.