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

Tests started hanging randomly after upgrading to Chrome 130 + TestCafe 3.7.0-rc.1 #8309

Open
thomas-jakemeyn opened this issue Oct 22, 2024 · 2 comments
Labels
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

@thomas-jakemeyn
Copy link

What is your Scenario?

We run 170+ TestCafe tests in Chrome headless within Docker. They used to be executed reliably in about 15 minutes in Chrome 129. After the upgrade to Chrome 130 + TestCafe 3.7.0-rc.1 (which solves #8286), the same tests now execute in about 30 minutes. After looking at the logs, we realised that some of them (but not always the same) seem to hang randomly.

Note that we don't use the spec reporter (see #8307). Also, we pass the following command line switches to Chrome:

--disable-fre --no-default-browser-check --no-first-run --disable-search-engine-choice-screen

What is the Current behavior?

Tests hang randomly in Chrome 130 whereas they used to be executed reliably in Chrome 129.

What is the Expected behavior?

Tests should not hang randomly in Chrome 130.

What is the public URL of the test page? (attach your complete example)

NA

What is your TestCafe test code?

NA

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

NA

TestCafe version

3.7.0-rc.1

Node.js version

No response

Command-line arguments

NA

Browser name(s) and version(s)

Chrome 130

Platform(s) and version(s)

Ubuntu 24.04 (Docker)

Other

No response

@thomas-jakemeyn thomas-jakemeyn added the TYPE: bug The described behavior is considered as wrong (bug). label Oct 22, 2024
@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 Oct 22, 2024
@thomas-jakemeyn
Copy link
Author

I just checked usage of CPU, disk and memory during test execution and everything seems perfectly fine. So the problem is apparently not related to a lack of resources.

Screenshot 2024-10-22 at 10 50 15

@thomas-jakemeyn
Copy link
Author

I tested with Chrome 130 + TestCafe 3.6.2 patched with a backport of this change and the behaviour is the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

1 participant