Flaky test-http2-too-many-streams

https://ci.nodejs.org/job/node-test-commit-plinux/15046/nodes=ppcbe-ubuntu1404/console

not ok 932 parallel/test-http2-too-many-streams
  ---
  duration_ms: 0.521
  severity: fail
  stack: |-
    (node:6590) ExperimentalWarning: The http2 module is an experimental API.

Ping @nodejs/http @nodejs/http2

I don't get these failures with no stack trace or signal code... No clue where to start. 😕

Yeah, they are pretty bad and happening often at the moment 😞.

@nodejs/build could someone look into these failures without strack traces or signal codes? I feel like these might be more CI or test runner related rather than failures of node or the test itself.

Are these failing on a specific platform? I'll investigate further. Triggering these reliably can be difficult.

The ones with no stack trace or signal code have all been on debian8 and ubuntu (I believe 1404 and maybe 1204).

And I strongly suspect this isn't http2 related. There have been many different tests that have failed this way, across the above mentioned systems. Everything from debug to zlib.

Happened again today https://ci.nodejs.org/job/node-test-commit-linux/17083/nodes=debian8-x86/console

I am closing the reports without stack traces. I have the feeling this got resolved. If they come back, we can check again what to do.

Navigation Menu

Repository navigation

Flaky test-http2-too-many-streams #18657

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Flaky test-http2-too-many-streams #18657

Description

Activity

apapirovski commented on Feb 8, 2018

BridgeAR commented on Feb 8, 2018

apapirovski commented on Feb 12, 2018

jasnell commented on Feb 12, 2018

apapirovski commented on Feb 12, 2018

apapirovski commented on Feb 12, 2018

mhdawson commented on Mar 14, 2018

BridgeAR commented on Mar 25, 2018

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions