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 execution is stuck while using Chrome Version 130.0.6723.59 #8312

Open
shyedhu opened this issue Oct 23, 2024 · 11 comments
Open

Testcafe execution is stuck while using Chrome Version 130.0.6723.59 #8312

shyedhu opened this issue Oct 23, 2024 · 11 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

@shyedhu
Copy link

shyedhu commented Oct 23, 2024

What is your Scenario?

Looks like Testcafe test execution is stuck while using Chrome Version 130.0.6723.59 with Testcafe Version 3.7.0-rc.1..

I also noticed this issue not happening on same chrome browser version if I was not using following the video option

--video artifacts/videos --video-options singleFile=true,failedOnly=false,pathPattern=${TEST_INDEX}/${USERAGENT}/${FILE_INDEX}.mp4

What is the Current behavior?

  • Chrome browser Version 130.0.6723.59 was opened and test execution is stuck for long hours
  • Firefox browser was opened and test executed successfully

What is the Expected behavior?

Test should execute successfully

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

none

What is your TestCafe test code?

https://github.com/shyedhu/testcafe-poc/blob/main/README.md

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

  1. git clone https://github.com/shyedhu/testcafe-poc.git
  2. cd testcafe-poc
  3. npm install
  4. npm run test:local:chrome

TestCafe version

3.7.0-rc.1

Node.js version

v22.3.0

Command-line arguments

NONE

Browser name(s) and version(s)

Chrome Version 130.0.6723.59 (Official Build) (x86_64)

Platform(s) and version(s)

MacOS Ventura Version 13.6.6

Other

No response

@shyedhu shyedhu added the TYPE: bug The described behavior is considered as wrong (bug). label Oct 23, 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 23, 2024
@ayemelyanenko-chegg
Copy link

I am also seeing this issue even without upgrading to TestCafe RC 3.7.0. The tests hang with --disable-native-automation and Chrome 130 and TestCafe version 3.6.2. The issue seems to be with this specific Chrome version 130.0.6723.69-1 which was released today, on October 22nd and that's when the issues started to happen. Seems to also happen on ubuntu/debian images as well

@deepanshugoyal1989
Copy link

I am also getting the same issue,....Testcafe test execution getting stuck while using Chrome Version 130.0.6723.59 with Testcafe Version 3.7.0-rc.1.

@Bayheck Bayheck added the STATE: Issue accepted An issue has been reproduced. label Oct 23, 2024
Copy link

We appreciate you taking the time to share information about this issue. We reproduced the bug and added this ticket to our internal task queue. We'll update this thread once we have news.

@github-actions github-actions bot removed STATE: Need response An issue that requires a response or attention from the team. STATE: Issue accepted An issue has been reproduced. labels Oct 23, 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 23, 2024
@josephgavin
Copy link

Hey I'm also having the same issue as the others here. Same version of chrome and testcafe. I upgraded testcafe because of the chrome error that was fixed with 3.7.0-rc.1, but now when I run my tests they just hang. This is in headless mode btw, based on context I think others had it not working in headed.

@jdnick27
Copy link

jdnick27 commented Oct 23, 2024

I am also running into this issue. We run through azure pipelines using agents but this is an issue on our local machines as well. We do run headless, but this is also an issue with out headless. We can an error about a websocket.

My testcafe does not "hang" it actually crashes and kills the run.

@shyedhu
Copy link
Author

shyedhu commented Oct 23, 2024

I am also running into this issue. We run through azure pipelines using agents but this is an issue on our local machines as well. We do run headless, but this is also an issue with out headless. We can an error about a websocket.

My testcafe does not "hang" it actually crashes and kills the run.

@jdnick27 you can try testcafe v3.7.0-rc.1 to resolve websocket issue

@shyedhu
Copy link
Author

shyedhu commented Oct 23, 2024

--video

I am also seeing this issue even without upgrading to TestCafe RC 3.7.0. The tests hang with --disable-native-automation and Chrome 130 and TestCafe version 3.6.2. The issue seems to be with this specific Chrome version 130.0.6723.69-1 which was released today, on October 22nd and that's when the issues started to happen. Seems to also happen on ubuntu/debian images as well

I was facing the issue only Chrome version 130 when i was enabled --video options in command line

@jdnick27
Copy link

that worked. Now I am seeing the same issue with the browser opening and what looks to be "hanging". I am seeing a white screen on test start. Is this what you are seeing @shyedhu ?

@ayemelyanenko-chegg
Copy link

As a workaround, if you have Microsoft Edge installed, you can use that for your tests for now as Edge is Chromium based

@Bayheck
Copy link
Collaborator

Bayheck commented Oct 25, 2024

Hello,

We have released TestCafe 3.7.0-rc.2, which addresses this issue. Please try it and let us know if the issue is gone.

@Bayheck Bayheck removed the STATE: Need response An issue that requires a response or attention from the team. label Oct 25, 2024
@JavaJung
Copy link

TestCafe 3.7.0-rc.2 looks good so far, on laptop and in ubuntu image run. Just prior to this update it seemed to work to remove screenshot and video options in testcaferc.json as a workaround

@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 25, 2024
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

7 participants