[CSR-3] Report results for spec files when cypress has a hard crash about cypress-cloud HOT 13 CLOSED

Hello @bilarallen I am very sorry that this issue is taking so much to resolve, we are working on a fix, expecting to roll out a release next week.

from cypress-cloud.

That's great! Will release to the latest npm channel

from cypress-cloud.

Randomly encountered it again but this time before the warning message it displays:

[1910:0314/060518.104073:ERROR:connection.cc(46)] X connection error received.
Gdk-Message: 06:05:18.108: Cypress: Fatal IO error 11 (Resource temporarily unavailable) on X server :99.

from cypress-cloud.

Thanks for reporting that @bilarallen. It seems like cypress had a hard crash without returning anything at all.

from cypress-cloud.

Hi @agoldis I think I found the possible root cause of the issue but I'm not that really sure, it seems that based on my comment #79 (comment) its a problem with the xvfb since I'm running the test in parallel all threads are using the same port so it resulted in not finding the test result of the recent run. Here's additional links that can connect the dot for this problem:

tnicola/cypress-parallel#89 (comment)
cypress-io/xvfb#98
https://docs.cypress.io/guides/continuous-integration/introduction#Xvfb

I get some point in the comment to run a particular command for xvfb but I don't know how to do it in my jenkins pipeline since it is using docker cypress/base image

from cypress-cloud.

@bilarallen are you running cypress in parallel on the same machine? It'd be still great to have the crash reported to the dashboard.

from cypress-cloud.

Hi @agoldis yes I am running the parallel test on the same machine.

from cypress-cloud.

Hello, we have the same issue. We are running our test in parallel on the same machine as well. @agoldis Do I understand you correctly the problem is that the Cypress cloud processes are running on the same machine. So running each cypress cloud process in a different docker container might solve the issue, right?

from cypress-cloud.

@MaltePetersen
Running on the same machine increases the chances of a crash because Cypress is quite resources-heavy.
Using isolated environments can prevent some crashes or side effects.

This issue deals is aboutcypress-cloud not reporting the results for crashed cypress runs and causing the whole run to time out

from cypress-cloud.

Hi @agoldis, would just like to ask what's the update for this one, please? As we have experienced it again. Here is the debug logs. Thanks!
Cypress_Cloud_Issue_79_New_Logs.txt

from cypress-cloud.

Hi @agoldis cool! Looking forward to it 😄 thanks!

from cypress-cloud.

@bilarallen @MaltePetersen
Very sorry it took so long to resolve. Please try using [email protected] - along with a bit faster reporting, it handles the failures in an appropriate way.

from cypress-cloud.

@agoldis Thanks for the update. Through the appropriate error handling, I recognized that my concurrent approach on the same machine did not work because xvfb was sometimes locked from the other cypress-cloud instance accessing it on initialization. Just putting a sleep 5 && before my second cypress-cloud initialization solved the issue.

from cypress-cloud.