-
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
"RangeError: Invalid time value" while upgrading to Debian 12 #27869
Comments
This comment was marked as outdated.
This comment was marked as outdated.
I'm running a custom Cypress docker image based on the node 18 image, and got the same error in my Gitlab CI pipeline last night:
It also happened in one of my Chrome pipelines for the same test:
My Dockerfile for the Cypress container is as follows:
The bug happens on versions 13.0.0, 13.1.0 and 13.2.0. So far it looks like it doesn't happen on 12.17.4. EDIT: Never mind, also happens on 12.17.4. |
I also encounter this error on 12.17.4 while running Cypress under docker. But only then DEBUG=cypress:* |
Which Docker image are you using and which version of Debian is it based on? If it is not a Cypress one, can you use one of the current Cypress Docker images? |
I have the same error on ubuntu 23.04. And also another one
Full log:
|
For everyones information: what returned a stable environment for me was downgrading to Node 16 and Cypress 12.17.4. |
What operating system are you running under? |
A Docker image that is based on the node:16 image. |
I'm using node v16.20.2 and cypress 12.17.4 and still have that problem. @Gamer1120 what exact version of node fixed the issue? |
Thanks for filling in that information. Node.js |
I ran https://github.com/cypress-io/cypress-example-kitchensink on Ubuntu It seems that the biggest challenge for this issue is to find a shareable reproducible example and then to find a bug which can be fixed. |
@MikeMcC399 regarding the stack trace, is there any change I can apply to the Cypress source code to get more information when the issue occurs ? I'm able to reproduce it quite easily but using a private repository. |
I guess we need some involvement from the Cypress engineering team to make any further progress. Perhaps @jennifer-shehane can suggest as she seems to be handling incoming issues these days. |
@MikeMcC399 Cypress |
I can run https://github.com/cypress-io/cypress-example-kitchensink successfully on |
I have the same error. Sometimes Cypress crashes with:
Cypress 12.17.3 |
@BillyTom Try cypress 13 |
i upgraded to Cypress For posterity: |
Thank you for your help regarding this issue. |
Current behavior
Cypress test execution randomly failed with the following error:
Desired behavior
No response
Test code to reproduce
I did not create an example to reproduce the issue yet.
Cypress Version
13.2.0
Node version
18.18.0
Operating System
Debian GNU/Linux 12 (bookworm)
Debug Logs
Other
I'm having this issue since I upgraded my Docker image used to execute the Cypress tests from Debian 11 to Debian 12.
This issue occurred randomly and quite often (like 30% of the time).
When I downgrade to Debian 11 without changing anything else, I don't have this issue anymore.
I don't think the debug log can help as this issue could randomly occurs at different stage of the execution of the tests.
Does anyone have any idea what is causing this problem?
The text was updated successfully, but these errors were encountered: