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

test: investigate flakiness - parallel/test-process-external-stdio-close #13586

Closed
refack opened this issue Jun 9, 2017 · 2 comments
Closed
Labels
flaky-test Issues and PRs related to the tests with unstable failures on the CI. freebsd Issues and PRs related to the FreeBSD platform. process Issues and PRs related to the process subsystem. test Issues and PRs related to the tests.

Comments

@refack
Copy link
Contributor

refack commented Jun 9, 2017

  • Version: master
  • Platform: freeBSD
  • Subsystem: test,process
919	parallel/test-process-external-stdio-close	
duration_ms	0.429
severity	crashed
stack	oh no!
exit code: CRASHED (Signal: 11)

https://ci.nodejs.org/job/node-test-commit-freebsd/9643/nodes=freebsd11-x64/

@refack refack added freebsd Issues and PRs related to the FreeBSD platform. process Issues and PRs related to the process subsystem. test Issues and PRs related to the tests. labels Jun 9, 2017
@apapirovski
Copy link
Member

@refack do you know if this is still an issue?

@maclover7 maclover7 added the flaky-test Issues and PRs related to the tests with unstable failures on the CI. label Dec 25, 2017
@apapirovski
Copy link
Member

I haven't seen this for a really long time so I'm going to close for now. We can reopen if it resurfaces or if anyone has a strong opinion on this particular issue.

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. freebsd Issues and PRs related to the FreeBSD platform. process Issues and PRs related to the process subsystem. test Issues and PRs related to the tests.
Projects
None yet
Development

No branches or pull requests

3 participants