-
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
Videos not viewable on Cypress Dashboard when videoCompression is set to 0 #24595
Comments
Hi @liambutler. Thank you for logging this. I am unable to recreate it with my own test projects. When you see the issue is the video corrupt locally? Or just on the dashboard? |
Hi @ryanthemanuel, thanks for getting back to me
Both, unfortunately! You can see other folks encountering the problem in this issue Some more info about my setup: Local machine: CI: Here's a run where you can see that the dashboard is unable to play the uncompressed recordings Hope that helps. Let me know if you need any more info |
Aha. Thanks for the additional information @liambutler. I was able to reproduce this. Key differences from when I tried before:
I will go ahead and route this to the e2e team. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior
I imagine that this is related to this issue
I've been trying to debug video frame skip issues when running Cypress via GitHub Actions (issue here). One thing that was suggested to me was to set the
videoCompression
to0
incypress.config.ts
.According to the GitHub Action's execution log, the upload was successful:
However, when looking at this run on the dashboard, the video is not watchable:
And there is this error in the console:
Desired behavior
No response
Test code to reproduce
Relevant config items:
Cypress Version
10.11.0
Node version
v16.18.0
Operating System
ubuntu-20.04
Debug Logs
I can email the run log if required, but would rather not share on here
Other
No response
The text was updated successfully, but these errors were encountered: