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.

Sign up for GitHub

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

Jump to bottom

Flaky parallel/test-http-get-pipeline-problem #18731

Closed
BridgeAR opened this issue Feb 12, 2018 · 3 comments
Closed

Flaky parallel/test-http-get-pipeline-problem #18731

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

Comments

@BridgeAR
Copy link
Member

https://ci.nodejs.org/job/node-test-commit-linux/16299/nodes=alpine36-container-x64/console

not ok 664 parallel/test-http-get-pipeline-problem
  ---
  duration_ms: 0.340
  severity: crashed
  stack: |-
    oh no!
    exit code: CRASHED (Signal: 11)

Ping @nodejs/http @nodejs/http2
@BridgeAR BridgeAR added http Issues or PRs related to the http subsystem. test Issues and PRs related to the tests. flaky-test Issues and PRs related to the tests with unstable failures on the CI. labels Feb 12, 2018
@rvagg
Copy link
Member

rvagg commented Mar 7, 2018

I reckon this is related to #18998. I think on alpine we see "CRASHED" but on debian and ubuntu we see an empty stack

@apapirovski

This comment has been minimized.

Sign in to view
@apapirovski
Copy link
Member

Duplicate of #18323 — failing for the same reasons that are not inherently related to the test.

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

No branches or pull requests
3 participants
@apapirovski @rvagg @BridgeAR