Closed marcelwgn closed 5 months ago
Hi @chingucoding , sorry to hear you're having issues. Are you able to provide us with Debug Logs of a failing run so we can try to diagnose what's going on?
Unfortunately we have to close this issue due to inactivity. Please comment if there is new information to provide concerning the original issue and we can reopen.
Sorry for the completely late reply. It seems our issue somehow didn't occur anymore, however I am able to reproduce this with upgrading cypress
to any version after 13.0
. The issue only occurs on first runs, the second, third ... run work just fine. The vite
version does not seem to matter. I would be able to provide you debug logs, however we would prefer not sharing that publicly depending on the loggers you want to see.
We can consistently reproduce this in our CI. Locally, all is well. We are working with the Cy team towards a resolution so Vite works well in CI.
@muratkeremozcan This has the same stack trace in v13? Can someone provide a way to reproduce?
We'll have to close this issue since there's no information to reproduce this.
Current behavior
Our component tests occasionally fail with the following two stacktraces:
and
Desired behavior
Tests should not occasionally crash due to outside of tests that doen't seem to originate from our code (at least looking at the stacktrace).
Test code to reproduce
So far we haven't found a reliable way to reproduce this, locally test runs are mostly fine. Running in GitHub Actions, error rate seems to be around 50%.
Cypress Version
12.15.0
Node version
20.2.0 locally, v16.16.0 in GitHub Actions
Operating System
10.0.22621.1848 locally, 22.04.2 in GitHub Actions
Debug Logs
No response
Other
This issue seemed to be fixed by downgrading our vite version from 4.3.9 to 4.1.1 seemed to have fixed this issue for us.