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 parallel/test-http-url.parse-path #18430

Closed
mmarchini opened this issue Jan 29, 2018 · 2 comments
Closed

Flaky parallel/test-http-url.parse-path #18430

mmarchini opened this issue Jan 29, 2018 · 2 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

@mmarchini
Copy link
Contributor

mmarchini commented Jan 29, 2018

  • Version: master
  • Platform: debian8-x86
  • Subsystem: http, test

First discovered in CI run of #18384, which doesn't have any changes related to http.

https://ci.nodejs.org/job/node-test-commit-linux/15920/nodes=debian8-x86/console

not ok 821 parallel/test-http-url.parse-path
  ---
  duration_ms: 0.169
  severity: fail
  stack: |-
  ...
@maclover7 maclover7 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 Jan 29, 2018
@starkwang
Copy link
Contributor

This can be reproduced through stress test (7 cases in 9999):
https://ci.nodejs.org/job/node-stress-single-test/1768/nodes=debian8-x86/console

@BridgeAR
Copy link
Member

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. http Issues or PRs related to the http subsystem. test Issues and PRs related to the tests.
Projects
None yet
Development

No branches or pull requests

4 participants