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 fails on starting #8389

Open
AlekseyKravtsov17 opened this issue Feb 27, 2025 · 2 comments
Open

Testcafe fails on starting #8389

AlekseyKravtsov17 opened this issue Feb 27, 2025 · 2 comments
Labels
STATE: Need clarification An issue lacks information for further research. STATE: Need response An issue that requires a response or attention from the team. TYPE: bug The described behavior is considered as wrong (bug).

Comments

@AlekseyKravtsov17
Copy link

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 approximately 30% of the executions fail randomly. The test code is exactly the same. We started to face this issue more frequently since February 26, 2025 10:52 GMT. Exactly after the update in Ubuntu 22.04 actions/runner-images@78d6387

Before this date the following issue occurred only 1-3 times per 1-3 weeks.

We hypothesized that it might be due to a chrome version update, and tried running the tests on the previous version, but they fail with the same frequency on both Google Chrome 133.0.6943.53 and 133.0.6943.126 versions

ERROR Cannot establish one or more browser connections.
1 of 2 browser connections have not been established:
- chrome:headless

Hints:
- Increase the Browser Initialization Timeout if its value is too low (currently: 2 minutes for all browsers). The timeout determines how long TestCafe waits for browsers to be ready.
- The error can also be caused by network issues or remote device failure. Make sure that your network connection is stable and you can reach the remote device.

Type "testcafe -h" for help.

The issue seems to be absolutely the same as it was there #8292
And according to the comments under this issue it still reproduces for many people.

Tests are running in GH hosted agents (runs-on: ubuntu-22.04) 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 we 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.7.0

Node.js version

v20

Command-line arguments

yarn testcafe

Browser name(s) and version(s)

No response

Platform(s) and version(s)

No response

Other

testcafe logs GH.log

@AlekseyKravtsov17 AlekseyKravtsov17 added the TYPE: bug The described behavior is considered as wrong (bug). label Feb 27, 2025
@testcafe-need-response-bot testcafe-need-response-bot bot added the STATE: Need response An issue that requires a response or attention from the team. label Feb 27, 2025
@Bayheck
Copy link
Collaborator

Bayheck commented Mar 3, 2025

Hello, try running your tests with the latest TestCafe v3.7.2 and let us know your results.

@Bayheck Bayheck added STATE: Need clarification An issue lacks information for further research. and removed STATE: Need response An issue that requires a response or attention from the team. labels Mar 3, 2025
@vasilyevi
Copy link

We switched to 3.7.2 and node 22.14.0, if fails much less, but still fails

@testcafe-need-response-bot testcafe-need-response-bot bot added the STATE: Need response An issue that requires a response or attention from the team. label Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
STATE: Need clarification An issue lacks information for further research. STATE: Need response An issue that requires a response or attention from the team. TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

3 participants