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

testcafe stuck with error "upstream connect error or disconnect/reset before headers" #3576

Closed
gal432 opened this issue Mar 18, 2019 · 6 comments
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot.

Comments

@gal432
Copy link

gal432 commented Mar 18, 2019

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:

  • testcafe version: 1.1.0
  • node.js version:10.14.2
  • command-line arguments: chromium:headless --no-sandbox /tests/e2e/tests/Tests/CITests/ --dev -r spec,xunit:/tests/e2e/tests/ui-test-results.xml
  • browser name and version: chromium / chrome 73
  • platform and version: Mac, Linux and testcafe docker image
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Mar 18, 2019
@gal432
Copy link
Author

gal432 commented Mar 18, 2019

When it happened not in chrome headless:
image
image

@gal432
Copy link
Author

gal432 commented Mar 19, 2019

From chrome headless:
image

@AlexKamaev
Copy link
Contributor

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.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Mar 19, 2019
@AlexKamaev AlexKamaev added the STATE: Need clarification An issue lacks information for further research. label Mar 19, 2019
@gal432
Copy link
Author

gal432 commented Mar 19, 2019

I'm sad to say that you right. its indeed coming from my env. I don't sure why (envoy with multiple proxies).
but for some reason when the testcafe gets this 503 page everything is stuck. No matter where I put a code to patch this problem (before / after in fixture, in the test itself), it will stuck the test process forever. any idea how I can patch this for now?

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Mar 19, 2019
@no-response no-response bot removed the STATE: Need clarification An issue lacks information for further research. label Mar 19, 2019
@AlexKamaev
Copy link
Contributor

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.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Mar 20, 2019
@lock
Copy link

lock bot commented Mar 30, 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 An issue has been automatically locked by the Lock bot. label Mar 30, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot.
Projects
None yet
Development

No branches or pull requests

2 participants