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

cypress/included:13.4.0 with problems when run for the 2nd time #990

Open
rgudwin opened this issue Nov 6, 2023 · 0 comments
Open

cypress/included:13.4.0 with problems when run for the 2nd time #990

rgudwin opened this issue Nov 6, 2023 · 0 comments

Comments

@rgudwin
Copy link

rgudwin commented Nov 6, 2023

I am trying to run cypress/included with the following bash script:

#! /bin/bash
SCRIPTPATH="$( cd "$(dirname "$0")" ; pwd -P )"
ID=`id -u`
GID=`id -g`
USER='user'
docker run \
-it \
--rm \
--name cypress \
-h cypress \
-w /home/$USER \
-v ${SCRIPTPATH}/:/home/$USER/ \
--net=host \
--entrypoint=bash \
-e DISPLAY=:0 \
cypress/included:13.4.0 \
-c "groupadd -g $GID $USER;useradd -r -d /home/$USER -s /bin/bash -g $USER -G sudo -u $ID $USER;su -c 'cypress open --browser edge'  $USER"

In the first time I run the script, it works without any problem ... I am able to run cypress, install the E2E tests and run them. The problem happens when I try to do it for the 2nd time, i.e., with all the E2E testings already configured. In this case, cypress opens, but when I select the project, it tries to open the project, but never finishes, i.e. it keeps forever trying to load it. I tried all versions of cypress/included 13, backwards until 13.0.0 and the same problem happens. With 12.17.4 it works without problems. Also, if I try to open a project created with 12.17.4 with 13.4.0, it works, even though it is already configured. It seems the E2E examples created by cypress 13 have something wrong that is preventing it to open the tests for the 2nd time.
Strangely, if I try to open a project created with 13.4.0 with 12.17.4 it opens, and after closing it, I can open it the next time with 13.4.0. But if I try to do that for a 2nd time, it stops working. Maybe a problem with a cache or something related ? It is important to remark that with 12.17.4 this problem does not occur at all !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant