Testcafe fails on starting #8292
Comments
vasilyevi
added
the
TYPE: bug
testcafe-need-response-bot
bot
added
the
STATE: Need response
|
Hello @vasilyevi, Without accurately reproducing the issue, it's difficult to determine what goes wrong. Could you please try running TestCafe with a debug log? To enable the debug log, you can do the following: set DEBUG=testcafe:*,hammerhead:*
testcafe chrome index.js 2> testcafe.logBefore running TestCafe, set the Please refer to the following help topic for details: https://testcafe.io/documentation/402636/faq/general-info#related-questions. |
PavelMor25
added
STATE: Need clarification
|
testcafe-need-response-bot
bot
added
the
STATE: Need response
github-actions
bot
removed
the
STATE: Need clarification
|
Hello @vasilyevi, Try to run Chrome with // configuration file
{
// ...
browsers: "chrome:headless --disable-search-engine-choice-screen",
// ...
} |
PavelMor25
added
STATE: Need clarification
|
It does not help |
testcafe-need-response-bot
bot
added
the
STATE: Need response
github-actions
bot
removed
the
STATE: Need clarification
|
Hello, We have released testcafe 3.7.0-rc.1, which might address this issue. Please test it and let us know your results. |
Bayheck
removed
the
STATE: Need response
|
Not OP, but I had this same issue and 3.7.0 fixed it |
testcafe-need-response-bot
bot
added
the
STATE: Need response
Bayheck
added
STATE: Need clarification
|
Also not the OP, but for us this issue is introduced since 3.7.0. We run the testcafe docker (chromium:headless) in the pipeline. It does not occur with every test job, but randomly (retry solves it). |
testcafe-need-response-bot
bot
added
the
STATE: Need response
|
This issue was automatically closed because there was no response to our request for more information from the original author. Currently, we don't have enough information to take action. Please reach out to us if you find the necessary information and are able to share it. We are also eager to know if you resolved the issue on your own and can share your findings with everyone. |
testcafe-need-response-bot
bot
removed
the
STATE: Need response
Still applicable for us with testcafe 3.7.0 and 3.7.1 : We had to revert to testcafe 3.6.2 to have successful pipelines again. |
testcafe-need-response-bot
bot
added
the
STATE: Need response
|
Hello, I believe we fixed this issue as it was also in our internal backlog. We have not yet released this fix. Hopefully, we will add it to our next release. Please stay tuned. |
Bayheck
removed
the
STATE: Need response
What is your Scenario?
We have a set of tests which executes every 30 mins 24/7
What is the Current behavior?
We have around 50 executions per day, but 3-6 executions might be randomly failed. The test code is exactly same.
The "concurrency" and "quarantineMode" options from the configuration file will be ignored.
ERROR Cannot establish one or more browser connections.
1 of 2 browser connections have not been established:
Hints:
Type "testcafe -h" for help.
There is no logs, screenshots and even before hook is not started. How can we determine what happens? Or let me know what can we provide additionally. Code is not relevant the the code itself works fine, sometimes something goes wrong with testcase itself.
Tests are running in GH hosted agents with concurrency 2. browserInitTimeout is already huge, no issue with app under test.
We also have similar configuration of executions with playwright, no similar issues there. So I don't think the reason in GH hosted agent.
What is the Expected behavior?
Should work as other ~45 executions
What is the public URL of the test page? (attach your complete example)
N/A
What is your TestCafe test code?
N/A
Your complete configuration file
module.exports = {
screenshots: {
path: "./artifacts/screenshots",
takeOnFails: false,
pathPattern: "${DATE}${TIME}/${TEST}/${FILE_INDEX}${QUARANTINE_ATTEMPT}.png",
thumbnails: false
},
disableMultipleWindows: true,
browsers: "chrome:headless",
concurrency: 2,
skipJsErrors: true,
browserInitTimeout: 120000,
pageLoadTimeout: 60000,
pageRequestTimeout: 65000,
selectorTimeout: 20000,
testExecutionTimeout: 900000,
quarantineMode: false,
disableNativeAutomation: false,
testResults,
}
Your complete test report
No response
Screenshots
No response
Steps to Reproduce
N/A
TestCafe version
3.6.0
Node.js version
v18
Command-line arguments
yarn testcafe
Browser name(s) and version(s)
No response
Platform(s) and version(s)
No response
Other
No response
The text was updated successfully, but these errors were encountered: