-
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
Close extra target cause Target.targetDestroyed, and then case failed #28916
Comments
@7999 Could you provide a reproducible example? Does this error happen on Cypress version prior to 13.6.0? |
2 this issue only happened after we update the version to 13.6.0. BTW, we update the version from 9.3.1 to 13.6.0 |
@7999 Could you try Cypress 13.5.1 to see if the issue is resolved in that version? |
@jennifer-shehane |
try version 13.5.1 and monitoring. |
@7999 Any updates? |
@jennifer-shehane |
@jennifer-shehane |
@jennifer-shehane |
@7999 Is this happening in newer versions? My assumption was that this was resolved. |
@jennifer-shehane |
Sorry, I got very confused in this thread. @7999 Have you tried any of our newer versions to see if this |
@jennifer-shehane |
This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided. |
This issue has been closed due to inactivity. |
Current behavior
case failed due to:
Desired behavior
No response
Test code to reproduce
it's sporadic
Cypress Version
13.6.0
Node version
18.17.1
Operating System
windows10 19045.3930
Debug Logs
Other
No response
The text was updated successfully, but these errors were encountered: