You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
09:53:40 not ok 529 sequential/test-http2-settings-flood09:53:40 ---09:53:40 duration_ms: 1.13909:53:40 severity: crashed09:53:40 exitcode: -107374181909: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.
Activity
mcollina commentedon Dec 14, 2018
cc @jasnell
mcollina commentedon Dec 14, 2018
Prior art: #18251 #19349.
mcollina commentedon Dec 14, 2018
cc @Trott
Trott commentedon Dec 14, 2018
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 commentedon Dec 14, 2018
Oh, wait, you wrote "master" above. Yeah, link would be good. Would want to know what Windows variant etc.
Trott commentedon Dec 14, 2018
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 commentedon Dec 14, 2018
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
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.
test: mark test-http2-settings-flood as flaky on Windows
Trott commentedon Dec 14, 2018
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?)
[-]flaky sequential/test-http2-settings-flood[/-][+][v8.x] flaky sequential/test-http2-settings-flood[/+]test: mark test-http2-settings-flood as flaky on Windows
MylesBorins commentedon Dec 22, 2018
marked flaky on 8.x in 2bedbdb
test: mark test-http2-settings-flood as flaky on Windows
BridgeAR commentedon Jan 2, 2020
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.