Open josh-atkins opened 7 months ago
I wasn't able to recreate this with the example on my Intel Mac. I'll have to get someone with an M1 to try it next.
Electron was updated in 13.6.5, so I would suspect that is the cause for this behavior.
Great - thanks!
Just adding - I'm also seeing this and can reproduce the issue from @josh-atkins github repo. I'm running an M1 Mac Sonoma 14.3.1.
This has been causing pain while dockerising our tests and I had no idea why!
Hey is there any solution, I have the same problem
I refer to this https://github.com/cypress-io/cypress-docker-images/blob/master/base/centos7/Dockerfile to build my image。 And I change nodejs to 16.x, it alwys hangs。 I also tried cypress/base, this works. I cannot use cypress/base in my company, I can only use centos to build images myself。 pc: Apply M2 Pro.
@mengfei0053 Our minimum supported version with recent versions of Cypress is Node 18+ https://docs.cypress.io/guides/getting-started/installing-cypress#Nodejs
@josh-atkins Are you utilizing Colima as the Docker container? I recently encountered the same issue and upon checking your demo repository, I found some information:
--vm-type=vz
command, it hangs in the same way as your problem.--vm-type=qemu
command, which is the default VM type for Lima, results in a "Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory" error in the Cypress verification step when Cypress runs.--arch x86_64 --vm-type=qemu
, Cypress logs the error "The "paths[1]" argument must be of type string. Received undefined" but the test still runs successfully.So, I think the problem might occur inside the Docker container(colima). Unfortunately, I don't have a Docker Desktop license, so I can't verify whether this problem also occurs on Docker Desktop.
Same issue here on M1 with MacOS 14.5, Cypress 13.6.4 works under Docker (this image) with --platform=linux/amd64
(using Rosetta 2) but later Cypress versions hang indefinitely.
This is a M(1 2 3) issue on macbooks... :/
My cypress tests works fine on a Lenovo and on our build server - but not on my Macook Pro M3 😦
Same issue on Mac OS 13.6 , processor M1
e2e-test | [SUCCESS] Verified Cypress! /root/.cache/Cypress/13.13.0/Cypress
e2e-test |
e2e-test | DevTools listening on ws://127.0.0.1:58611/devtools/browser/ff0bfa3a-3e9d-4a26-9ad6-aee0b7212352
e2e-test | Couldn't find tsconfig.json. tsconfig-paths will be skipped
it hangs.
I wasn't able to recreate this with the example on my Intel Mac. I'll have to get someone with an M1 to try it next.
Electron was updated in 13.6.5, so I would suspect that is the cause for this behavior.
@jennifer-shehane any updates on this? From my conversation with our Cypress TAM I understand that access to M1 and M2 architecture at Cypress is limited but we are severely impaired by this as our local environment doesn't match the tests in CI and produces inconsistent results.
Current behavior
Setup
cypress run
fails with 13.6.5 and 13.6.6When using cypress version 13.6.5 and 13.6.6, executing
cypress run
fails as it just hangs right after announcing it is about to start the test.DEBUG: cypress:*
prints this before hanging:The entire debug output of
DEBUG: cypress:*:error
is:And it hangs as follows:
cypress run
succeeds with 13.6.4When using cypress version 13.6.4 with the setup otherwise identical, the test completes as expected except it instead prints this message:
Desired behavior
cypress run
executes successfully with the latest version, without hanging, and without error messages.Test code to reproduce
docker compose run --interactive --build --rm cypress
cypress run
Cypress Version
13.6.6
Node version
v20.11.0
Operating System
macOS 14.4
Debug Logs
Other
I've had a look at the
cypress:snapshot:error
to see if I can work out where it's coming from, but it appears on 13.6.4 which runs successfully so I'm not sure it's related to this error.I've also searched the logs for the term "error" which showed that
playwright-webkit
is missing, but when I installed this locally it didn't have resolve the issue.