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

"Unhandled exception in spawn: Error writing to socket: Broken pipe (Errno)" in socket client specs #7401

Closed
asterite opened this issue Feb 9, 2019 · 1 comment · Fixed by #7402
Closed

"Unhandled exception in spawn: Error writing to socket: Broken pipe (Errno)" in socket client specs #7401

asterite opened this issue Feb 9, 2019 · 1 comment · Fixed by #7402
Labels
kind:bug A bug in the code. Does not apply to documentation, specs, etc. kind:specs

Comments

@asterite
Copy link
Member

asterite commented Feb 9, 2019

If you put a 1000.times do around all socket client specs this is easy to reproduce. I won't have time these days to find out why it happens, but if somebody has the time, please investigate it.

With that and my other researches we should be reaching a point where no specs will fail on CI.
@asterite asterite added kind:bug A bug in the code. Does not apply to documentation, specs, etc. kind:specs labels Feb 9, 2019
@asterite asterite mentioned this issue Feb 9, 2019
Merged
@straight-shoota
Copy link
Member

This should probably be fixed by #7197

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind:bug A bug in the code. Does not apply to documentation, specs, etc. kind:specs
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

HTTP::Client spec: don't write server response if expecting read timeout asterite/crystal-1
2 participants
@asterite @straight-shoota