Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
BridgeAR opened this issue Feb 8, 2018 · 8 comments
Closed

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

BridgeAR opened this issue Feb 8, 2018 · 8 comments
Labels
flaky-test Issues and PRs related to the tests with unstable failures on the CI. http2 Issues or PRs related to the http2 subsystem. test Issues and PRs related to the tests.

Comments

@BridgeAR
Copy link
Member

BridgeAR commented Feb 8, 2018

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

@BridgeAR BridgeAR added test Issues and PRs related to the tests. flaky-test Issues and PRs related to the tests with unstable failures on the CI. http2 Issues or PRs related to the http2 subsystem. labels Feb 8, 2018
@apapirovski
Copy link
Member

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

@BridgeAR
Copy link
Member Author

BridgeAR commented Feb 8, 2018

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

@apapirovski
Copy link
Member

@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.

@jasnell
Copy link
Member

jasnell commented Feb 12, 2018

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

@apapirovski
Copy link
Member

apapirovski commented Feb 12, 2018

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

@apapirovski
Copy link
Member

apapirovski commented Feb 12, 2018

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.

@mhdawson
Copy link
Member

@BridgeAR
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky-test Issues and PRs related to the tests with unstable failures on the CI. http2 Issues or PRs related to the http2 subsystem. test Issues and PRs related to the tests.
Projects
None yet
Development

No branches or pull requests

4 participants