-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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 fails on the 8th test in CI #2265
Comments
This comment has been minimized.
This comment has been minimized.
@kristiehowboutdat this is unfortunately now a known issue. We've spent a lot trying to debug it and understand why it's happening. We issued a PR in Unfortunately, it did not. The challenge here is that it's extremely difficult to reproduce and seems to only happen on various CI providers. The only way we can gain an understanding is with the Cypress DEBUG logs. To clarify, you haven't done anything wrong on your end, it's an issue with Cypress - however it's only an issue with Electron and if you switched to Chrome in CI, it would just work. Our docker containers have Chrome built in. If you can reliably recreate this problem, then by enabling the DEBUG logs it will help us track it down. To enable those run: You can check these other issues as they are all users with the same problem: |
Thanks for your feedback. I've switched to use Will report back if there are any updates! |
hello any updates on this bug, were currently experiencing this on our third test. we try to change hierarchy of the file but it always failed on third. were using cypress 3.1.5 @brian-mann can you please help us. my test always hang on the 3rd test. |
@jbpallingayan We cannot begin to look at this issue until someone provides us with a reproducible example, so no, there are no updates on this bug. Can anyone provide an example of test code + app code we can run to see this bug? |
here is my temporary solution on this bug, i created two spec file that has no assertions it only runs a test my test will pass and it will not get sa same error again. i run with debug mode but i get the same error code waiting for response but when i try to run in gui electron i catch the bug and our keeps hanging on the same line of code. @jennifer-shehane update on this we experience this only on electron 59, is there a way that we can run our test on ci headless? or any recommendations that we can use chrome to run at our ci? |
@jbpallingayan You can pass a |
we cannot move to our project because of random hang of cypress we cannot find any issues on both it will just hang randomly, even on headless chrome and electron. we cannot share our app code or i can share my screen to you if you have time. @jennifer-shehane |
@jbpallingayan Is this during |
sigh.. @jennifer-shehane we fix it and its only our fault. thank you for helping me on this. :) |
@jbpallingayan Great! Any updates on how you fixed the issue would be helpful to add here - as I'm sure someone else will run into the same issue. |
its on our app, error message is hidden when the user spam login on our app. im very sorry for this. its not a bug on cypress. @jennifer-shehane |
Unfortunately we'll have to close this issue if no reproducible example is provided. Can anyone provide a way to reproduce this? |
Our tests always fail midway through the spec files, usually between files 8 and 14. I can't see anything helpful in these logs but if you tell me what else I could provide I would help out how I can without debug mode:
with debug mode:
|
@jennifer-shehane could you please provide what exit code 143 means? |
https://www.google.com/search?q=exit+code+143 Exit Code 143: Indicates failure as container received SIGTERM. |
We also have this issue on every pipeline, it send interrupt signal and aborts the execution. Can someone help if you have find solution for this? |
Any help from cypress team could be really helpful since we are basically stuck with every single pipeline in ci. |
Hi @AnushaAshokReddy This issue is quite old and I am guessing you have a different setup than OP. please open a new issue with a reproducible example. |
Current behavior:
Our cypress tests intermittently fail to open / execute a file, only on version
3.0.x
.When they do fail, it is always the 8th test. I even created a very simple test file as the 8th one to confirm this suspicion.
Sample failure:
Contents of
08_empty_test_should_pass.js
:Desired behavior:
Tests do not hang when opening the 8th (or any other) test file.
Steps to reproduce:
I'm not really sure what to put here since I can't repro it reliably, but here's the environment.
Buildkite with a docker container (
cypress/base:8
)Set up more than 8 tests.
Run the tests a bunch of times.
If the tests fail, notice that it's always the 8th test, no matter what is in that file.
Versions
Cypress:
3.0.3
. We've been experiencing this issue on every3.0.x
version. We've had to revert to2.x
where this issue has never happened.| │ Cypress: 3.0.3 │
| │ Browser: Electron 59 (headless) │
| │ Specs: 14 found │
The text was updated successfully, but these errors were encountered: