-
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
If video failed uploading, do not send video.url #3715
Comments
Hi @jennifer-shehane, I am running my tests on GitHub actions and tests are running fine but the video is not uploading to dashboard. I see this in the output "
Is this issue resolved? Thanks! |
Surfacing the same issue in our setup. After the spec, failed testcases videos are uploading. At the end got this failure.
|
I also had the exact same issue with the screenshot in Cypress Dashboard. is the fix coming soon?
|
I also had the same issue with a video upload. if it fails then the whole suite is timed out. thats really bad! |
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. |
@jennifer-shehane commented on Thu Jun 14 2018
Within run:
Yet, the video
url
is sent with an aws link still.https://dashboard.cypress.io/#/projects/m7bnkc/runs/4/specs
@brian-mann commented on Thu Jun 14 2018
The API doesn't actually know whether or not the uploading failed. It just assumes it was all successful.
For us to capture this state we would either need to send it along from the desktop client - or we'd need a lambda function to spawn in response to files being uploaded to buckets - which would then update the DB state.
Although it would be initially easier to do this out of the clients, its unnecessary and much less flexible (it wouldnt work on older versions) and I think we'd rather opt to go the lambda route because we will have to do that anyway when we do things like log processing.
The text was updated successfully, but these errors were encountered: