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

[WebSocket]: Error: write ECONNABORTED #1744

Closed
miherlosev opened this issue Sep 4, 2018 · 2 comments
Closed

[WebSocket]: Error: write ECONNABORTED #1744

miherlosev opened this issue Sep 4, 2018 · 2 comments
Assignees
Labels
AREA: server !IMPORTANT! STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Milestone

Comments

@miherlosev
Copy link
Contributor

Reproduced on farm with http://www.upworthy.com site.

http://ccnet.devexpress.devx/ccnet/server/farm/project/TESTCafe+Health+Monitor+(hammerhead_git)/build/log20180831220003.xml/ViewBuildReport.aspx

@cor3000
Copy link

cor3000 commented Sep 21, 2018

maybe this helps:
I encountered the same error message when running on nodejs 8.5.0 (on windows 10 64bit),

node_modules\testcafe-hammerhead\lib\request-pipeline\connection-reset-guard.js:27
    throw err;
    ^

Error: write ECONNABORTED
    at _errnoException (util.js:1026:11)
    at Socket._writeGeneric (net.js:758:25)
    at Socket._write (net.js:777:8)
    at doWrite (_stream_writable.js:387:12)
    at writeOrBuffer (_stream_writable.js:373:5)
    at Socket.Writable.write (_stream_writable.js:290:11)
    at Socket.write (net.js:695:40)
    at TLSSocket.ondata (_stream_readable.js:642:20)
    at emitOne (events.js:115:13)
    at TLSSocket.emit (events.js:210:7)

the error disappeared when switching to version 10.0.0

@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked Issues that were automatically locked by the Lock bot label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AREA: server !IMPORTANT! STATE: Auto-locked Issues that were automatically locked by the Lock bot TYPE: bug
Projects
None yet
Development

No branches or pull requests

3 participants