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

Keep getting constant Error: Still waiting to connect to Edge, retrying in 1 second #28103

Closed
CloneOfAlex opened this issue Oct 20, 2023 · 5 comments
Labels
type: duplicate This issue or pull request already exists

Comments

@CloneOfAlex
Copy link

Current behavior

When running tests in GitHub Actions
Keep getting constant Error: Still waiting to connect to Edge, retrying in 1 second

This behavior began around 48 hours ago

image

19s
DevTools listening on ws://12[7](https://github.com/Foundant/cypress-tests/actions/runs/6591472100/job/17910117529#step:4:7).0.0.1:33475/devtools/browser/dd527eb[8](https://github.com/Foundant/cypress-tests/actions/runs/6591472100/job/17910117529#step:4:8)-bf[9](https://github.com/Foundant/cypress-tests/actions/runs/6591472100/job/17910117529#step:4:9)9-479a-84bb-4ddc20f0d875
[1745:[10](https://github.com/Foundant/cypress-tests/actions/runs/6591472100/job/17910117529#step:4:10)20/123626.443847:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type: 
Displaying Cypress info...
Detected 4 browsers installed:
1. Chrome
  - Name: chrome
  - Channel: stable
  - Version: [11](https://github.com/Foundant/cypress-tests/actions/runs/6591472100/job/17910117529#step:4:11)8.0.5993.70
  - Executable: google-chrome
2. Chromium
  - Name: chromium
  - Channel: stable
  - Version: 118.0.5993.0
  - Executable: chromium-browser
3. Edge
  - Name: edge
  - Channel: stable
  - Version: 118.0.2088.46
  - Executable: microsoft-edge
4. Firefox
  - Name: firefox
  - Channel: stable
  - Version: 118.0.2
  - Executable: firefox
Note: to run these browsers, pass <name>:<channel> to the '--browser' field
Examples:
- cypress run --browser firefox
- cypress run --browser chrome
Learn More: https://on.cypress.io/launching-browsers
Proxy Settings: none detected
Environment Variables: none detected
Application Data: /home/runner/.config/cypress/cy/development
Browser Profiles: /home/runner/.config/cypress/cy/development/browsers
Binary Caches: /home/runner/.cache/Cypress
Cypress Version: [13](https://github.com/Foundant/cypress-tests/actions/runs/6591472100/job/17910117529#step:4:13).3.2 (stable)
System Platform: linux (Ubuntu - [22](https://github.com/Foundant/cypress-tests/actions/runs/6591472100/job/17910117529#step:4:22).04)
System Memory: 7.[26](https://github.com/Foundant/cypress-tests/actions/runs/6591472100/job/17910117529#step:4:26) GB free 6.06 GB

Desired behavior

We expect for browser to be found and tests to run - same way as it did 48 hour ago ..

Test code to reproduce

cant share at this time

Cypress Version

13.3.2

Node version

20.5

Operating System

ubuntu latest

Debug Logs

19s
DevTools listening on ws://127.0.0.1:33475/devtools/browser/dd527eb8-bf99-479a-84bb-4ddc20f0d875
[1745:1020/123626.443847:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type: 
Displaying Cypress info...
Detected 4 browsers installed:
1. Chrome
  - Name: chrome
  - Channel: stable
  - Version: 118.0.5993.70
  - Executable: google-chrome
2. Chromium
  - Name: chromium
  - Channel: stable
  - Version: 118.0.5993.0
  - Executable: chromium-browser
3. Edge
  - Name: edge
  - Channel: stable
  - Version: 118.0.2088.46
  - Executable: microsoft-edge
4. Firefox
  - Name: firefox
  - Channel: stable
  - Version: 118.0.2
  - Executable: firefox
Note: to run these browsers, pass <name>:<channel> to the '--browser' field
Examples:
- cypress run --browser firefox
- cypress run --browser chrome
Learn More: https://on.cypress.io/launching-browsers
Proxy Settings: none detected
Environment Variables: none detected
Application Data: /home/runner/.config/cypress/cy/development
Browser Profiles: /home/runner/.config/cypress/cy/development/browsers
Binary Caches: /home/runner/.cache/Cypress
Cypress Version: 13.3.2 (stable)
System Platform: linux (Ubuntu - 22.04)
System Memory: 7.26 GB free 6.06 GB

Other

No response

@MikeMcC399
Copy link
Contributor

@CloneOfAlex

We're seeing delays in CI on https://github.com/cypress-io/github-action/actions/workflows/example-edge.yml using Edge

for example https://github.com/cypress-io/github-action/actions/runs/6589879261/job/17905293268 on

https://github.com/actions/runner-images/blob/ubuntu22/20231016.1/images/linux/Ubuntu2204-Readme.md which merged 2 days ago and bumped Microsoft Edge from 117.0.2045.47 to 118.0.2088.46 on ubuntu-22.04 (aka ubuntu-latest)

image

image

I assume this is related. There doesn't seem to be any difference between Cypress 13.3.1 in this run and 13.3.2 which I also tried out (hasn't been merged yet - waiting for PR cypress-io/github-action#1061).

Connection problems to Edge have been going on for a while. In the github-action repo they have however generally not led to test failure.

@MikeMcC399
Copy link
Contributor

@CloneOfAlex

I'm seeing Edge also slow to start on a local Ubuntu 22.04 machine, although in a second Cypress test in the same session there are no waiting messages shown.

I can't reproduce the issue that the connection from Cypress to Edge fails completely. I only see it slow to connect, which makes me think it may be a performance issue.

I also noticed on GitHub that running in a Cypress container there were no waiting messages. I can't say it that would workaround your issue, but you might like to just try it out, for instance:

    runs-on: ubuntu-latest
    container:
      image: cypress/browsers:node-20.6.1-chrome-118.0.5993.88-1-ff-118.0.2-edge-118.0.2088.46-1
      options: --user 1001

@MikeMcC399
Copy link
Contributor

@jennifer-shehane jennifer-shehane added the type: duplicate This issue or pull request already exists label Nov 2, 2023
@CloneOfAlex
Copy link
Author

How is this completed - problem with Edge is still real and we dont have issues with Chrome BTW

@jennifer-shehane
Copy link
Member

This was closed as a duplicate.

@cypress-io cypress-io locked and limited conversation to collaborators Nov 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants