-
Notifications
You must be signed in to change notification settings - Fork 674
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
testcafe stuck with error "upstream connect error or disconnect/reset before headers" #3576
Comments
We didn't face such an issue and it does not look related to TestCafe. I think it's somehow related to your project/environment. So, please provide us with a working example which demonstrates the issue. |
I'm sad to say that you right. its indeed coming from my env. I don't sure why (envoy with multiple proxies). |
Since the issue can be related to DevExpress/testcafe-hammerhead#1961 as you mentioned, I think it's better to wait for the fix. So I'll close this issue as duplicate. If the fix of DevExpress/testcafe-hammerhead#1961 does not help, feel free to open a new issue with an example providing detailed information. |
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. |
What is your Test Scenario?
navigate to site
What is the Current behavior?
before the test even starts, I'm getting "upstream connect error or disconnect/reset before headers" in the browser. no indicative error on the process. the test itself will stuck forever
What is the Expected behavior?
No error / timeout in case of failure in setup the browser & exit failure
Steps to Reproduce:
Statistic bug. should be run in loops to make this reproduce. I see it more often when I run the tests in CI (after I saw the tests got stucked in my CI server, I tunneled & connected to the chromium debugging port and saw this message)
Debug logs didn't help since its even before the tests starts. in the fixture level and I don't get any logs about it when DEBUG=*
Your Environment details:
The text was updated successfully, but these errors were encountered: