-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Failing tests marked as skipped upgrading from 13.1.0 to 13.2.0 (up to 14.1.0) [arm/aarch64] #31193
Comments
@lemonad We don't have any specific logic to handle things differently in aarch64. I'd suggest narrowing this down to a super simple example - no app code, no CI setup, no plugins (no grep/fail fast), no 'rerunning in CI', no external reporters. I'm having a hard time reasoning how Cypress could be executing logic to skip all the tests until a normal first time run. I wasn't able to reproduce it on my macOS, but you also said it's not reproducible there. |
@jennifer-shehane I don't think I know how to make it simpler than the two files I included above (I basically followed the Cypress install/create your first test instructions and then added the Our Github CI is also running on the same hardware/Yocto so that doesn't help with replication. It might just be a special case unfortunately. We can use 13.1.0 for now, but it would be nice to be able to upgrade in the future. The changelog for 13.2.0 is short and it feels like the Electron update might have something to do with it. The 13.1.0 container runs Electron 106 and Node 20.5.0 while the 13.2.0 container runs Electron 114 and Node 20.6.1. |
@lemonad Have you tried running the tests in Chrome to exclude Electron as a browser issue? |
@jennifer-shehane Oh, that's a good suggestion! I just have to figure out which docker image to use and then I'll try it. |
In Discord https://discord.com/channels/755913899261296641/1344786011510542356 we discussed that the repro git clone --branch test/fail https://github.com/MikeMcC399/cypress-docker-images
cd cypress-docker-images
cd examples/basic-mini
docker run -it --rm -v .:/app -w /app cypress/included works as expected on GitHub-hosted runners and fails with the error
on the problematic Ubuntu 18 host. Docker no longer lists Ubuntu 18 as actively supported (see https://docs.docker.com/engine/install/ubuntu/ with minimum Ubuntu Focal 20.04 (LTS)). Docker removed support for Ubuntu 18.04 with docker/docs@c770500 on Jun 21, 2023. |
The issue is not reproducible on CircleCI with the machine image ubuntu-2004:2023.10.1 containing Docker This is an active runner on Ubuntu Possibly there is a Docker compatibility issue with the custom Yocto distribution built on Ubuntu |
Do you have an alternate NVIDIA Jetson Xavier NX module to test on, in case the |
Please let us know your plans for this issue. It appears that you are using Docker in an unsupported environment and unless the Cypress issue can be reproduced in a supported environment it is going to be difficult for the Cypress.io team or the community to help you further. |
I suggest to close this issue as there hasn't been any further feedback. |
Update:
I've added a minimal test setup below and it seems like this might be a combination of two things. Starting with 13.2.0, I get an error
and when also adding
defaultCommandTimeout: 8000
to the config, failing tests are marked as skipped silently.In 13.1.0, I get the expected response
Current behavior
After upgrading to version 14.1.0 we noticed failing tests silently being marked as skipped. Once a failing test is executed, that test and all subsequent tests are marked as skipped. Thus CI will always give a green checkmark.
Not making any modifications and running on macOS works as expected, leading me to believe that the problem might have to do with arm/aarch64 but not only that. Now, we are executing the
cypress/included
docker containers on an embedded device with a custom Yocto distribution built on Ubuntu 18.04.5 LTS. However, as the tests are being run inside the container, I think that has little bearing on the problem. I binary searched through all versions and found that 13.1.0 is the last version that works as expected and 13.2.0 skips tests.Our tests are very basic, like below. The configuration is without support files or hooks. We start the web server externally so cypress is just pointing to
http://localhost:80
viabaseUrl
.Example with a failing test at the top of the test file:
Example with the same test moved last
Using exactly the same test files with cypress/included:13.1.0, the results are as expected
Desired behavior
No response
Test code to reproduce
cypress.config.js:
cypress/e2e/spec.cy.js:
Cypress Version
14.1.0
Node version
The versions that come with the
cypress/included
docker containersOperating System
Ubuntu 18.04.5 LTS on aarch64
Debug Logs
I can add these but not sure if I should add the results from 13.2.0 or 14.1.0.
Other
No response
The text was updated successfully, but these errors were encountered: