Hangs indefinitely while running tests

[egucciar]

Current behavior:

While running my tests, Cypress suddenly stops responding. It will not continue running tests...

Desired behavior:

It shouldnt hang indefinitely with no way of me knowing why

How to reproduce:

not sure, i have a giant test suite with a loop. it was working fine until it wasnt.

Test code:

gigantum test suite

Additional Info (images, stack traces, etc)

• Operating System: Win 10
• Cypress Version: 1.4.1
• Browser Version: 62

[egucciar]

Just to note, i do not see anything SPECIFICALLY wrong with these test cases, but its certainly a few specific cases having this issue. Any ideas what may even cause indefinite hanging? Like hours long hanging on one test which runs fine in the runner?

[ksmahesh]

I do see behavior like this on jenkins run.
Enabling debug (DEBUG cypress:*) I see continuous output such as this

Fri, 09 Feb 2018 19:57:19 GMT cypress:server:timers child sending timer id 437 Fri, 09 Feb 2018 19:57:19 GMT cypress:server:timers child sending timer id 438 Fri, 09 Feb 2018 19:57:19 GMT cypress:server:timers child sending timer id 439 Fri, 09 Feb 2018 19:57:19 GMT cypress:server:timers child sending timer id 444 Fri, 09 Feb 2018 19:57:23 GMT cypress:server:timers child sending timer id 449 Fri, 09 Feb 2018 19:57:26 GMT cypress:server:timers clearing timer id 452 from queue { '452': { args: [], ms: 85000, cb: [Function] } } Fri, 09 Feb 2018 19:57:26 GMT cypress:server:timers queuing timer id 453 after 85000 ms Fri, 09 Feb 2018 19:57:26 GMT cypress:server:timers child received timer id 453 Fri, 09 Feb 2018 19:57:36 GMT cypress:server:timers child sending timer id 450 Fri, 09 Feb 2018 19:57:51 GMT cypress:server:timers clearing timer id 453 from queue { '453': { args: [], ms: 85000, cb: [Function] } } Fri, 09 Feb 2018 19:57:51 GMT cypress:server:timers queuing timer id 454 after 85000 ms Fri, 09 Feb 2018 19:57:51 GMT cypress:server:timers child received timer id 454

it continues to print out cypress:server:timers repeatedly without terminating.

Is there a way to terminate cypress process in such scenarios? Because I see this to happen repeatedly in my test suite.

[egucciar]

This is kind of a huge deal breaker / blocker in terms of us using cypress. I wish there was more visibility on the issue.

[jennifer-shehane]

@egucciar We really need a reproducible code example/repo to be able to begin work on this. There are an infinite number of variables that could be involved.

[egucciar]

@jennifer-shehane

considering the code / test suite is private intranet code (non public, id be breaking my NDA if i shared it) I can't actually make it public. Any suggestions on how to go about this? Capturing logs or anything ?

[kartikupreti]

I do see similar behavior of hanging without failing on Jenkins 2.0.105 run headless using the electron browser.

I do not have a large test suite either, the tests complete fine and the video gets saved but cypress doesn't quit after that and hangs just like that, on putting Debug to the command I see such messages over and over (just pasting a part of it)

cypress:server:timers child sending timer id 614
cypress:server:timers clearing timer id 617 from queue { '617': { args: [], ms: 85000, cb: [Function] } }
cypress:server:timers child received timer id 618

[ksmahesh]

@kartikupreti @egucciar dont you wish for a timeout functionality? Something that kills the cypress tests after say 10 mins?
I am using that hack right now in cypress/support/index.js where I use a setTimeout method to call window.close after pre-determined timeout.
Agreed, its a hack and it skips the remaining tests in spec file. But its definitely better than to have a continuously running process on Jenkins.
@jennifer-shehane I will try to provide with the script to reproduce this issue this weekend.

[michael-langley]

FWIW I have seen this behavior a couple of times on the initial page load. A couple of times it killed the suite (which is fine) but other times it runs indefinitely. However I see it more so when a cy.request() returns a 500 ISE or a 504 error.

[kartikupreti]

@mlangley2010 I think The issue you are getting is different (and might just be specific to your application/gateway not responding/forwarding the response to the UI on time.. just increasing the pageLoadTimeout from cypress.json should help in your case)

@ksmahesh The kill functionality can be implemented probably just by putting a timeout around that stage/step in jenkins?
Im concerned as to why it happens or rather what is cypress expecting, since it happens inconsistently and I've not been able to reproduce it on my local system.

[kartikupreti]

Duplicate of #674

[brian-mann]

@ksmahesh check out this issue. #1333 (comment)

You're seeing the timers continue to fire because the Browser is still open. So something is failing with closing the browser.

[michael-langley]

@kartikupreti It appears to not be happening anymore today. But no matter what I had the timeout set to Cypress would not advance past that failed step. My timeout was set to 60 seconds, and you can see the test had been running for 245.60, and that was the only step I had tried to run. Regardless, it sounds like the comment posted above in #1333 is a plausible explanation.

Thanks!