CypressError: cy.screenshot() timed out waiting '30000ms' to complete.

[kodriscollics]

Current behavior

I run my tests headless. After upgrading to Cypress 8.7.0, whenever a test fails for whatever reason, I get the following:

 CypressError: `cy.screenshot()` timed out waiting `30000ms` to complete.

That is all I get on the console. No other messages. I have to rerun the test(s) in the GUI environment to see what really happened and to get the real error.

The above error is masking what is happening on test failure.

The problem goes away when I back-rev Cypress to version 8.5.0.

Another aspect that makes this an even worse problem is that once the error is thrown, the session never exits so the test never really finishes.

Desired behavior

Show the real error instead of masking it with this faux error.

Test code to reproduce

Not sure this is practical, as I have tons of tests and any failure on any test results in the problem.

Cypress Version

8.6.0
8.7.0
9.0.0

Other

No response

[pawelgielda]

Hey, could it be connected with the last changes introduced with: c0d781d ?? The default timeout also changed for example in cy.request() method.

[szamanr]

do you also experience slower runtime or video playback issues, like in #18740 or #18564?

[Arunk28]

am facing the issue after updating the 8.6.0.
I will also revert and check to 8.5.0.

but please fix this because of this all test are failed
@jennifer-shehane

[kodriscollics]

@szamanr I have not noticed the tests running slower nor video playback issues.

[kodriscollics]

Same issue with Cypress version 9.0.0:

CypressError: `cy.screenshot()` timed out waiting `30000ms` to complete.

Test that complete successfully under 8.5.0 fail under 9.0.0. And, when the error occurs, the tests never exit.

[jennifer-shehane]

Duplicate of #5016

[theTestingApproach]

Hello, i am facing this same issue in 12.16.0..Any resolution so far please?

[wongk]

+1

[fzampori-sumo]

+1

[hannamarkevich]

• v12.9

[nagash77]

As @jennifer-shehane mentioned in this comment this ticket is a duplicate of #5016 . Please follow that ticket for any updates on this issue.