-
Notifications
You must be signed in to change notification settings - Fork 174
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
Something wrong with keep-alive agent sockets - networking hangs on OS level #2149
Comments
Thank you for the provided details. I've reproduced the error. We need time to research this problem. |
As a hint, I've injected into your code |
… on OS level` (close DevExpress#2149)
… on OS level` (close DevExpress#2149)
… on OS level` (close DevExpress#2149)
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. |
Steps to Reproduce:
Following test
node_modules/testcafe-hammerhead/lib/request-pipeline/destination-request/agent.js
adding the following at the end of file./node_modules/.bin/testcafe chrome:headless index.js -c 10
agent.js
and uncomment the line in interval function withresetKeepAliveConnections()
agent.destroy()
in the middle of test) all of 1000 tests were executed and most of them passed (see end of my log)Your Environment details:
I guess it's the cause of what was reported here DevExpress/testcafe#2864 and probably many other issues with hanging browser.
My blind guess would be it might have something to do with HTTP 206 partial content responses 🤷♀
The text was updated successfully, but these errors were encountered: