cypress: Test retries, when retrying on several failed tests, causes hanging in `cypress run`

Hi, I am running cypress and tests using docker inside the Jenkins pipeline. Unfortunately when the test failing cypress is hanging on with test retries attempt I suppose that in both attempts the test fails but no idea why cypress didn’t go on after it. Could anyone help me with this or explain if it is a bug or wrong usage? I am trying to search for any issue with this case but didn’t find it. Screen from the pipeline:

I’ve experimented with different ways for adding test retries to my tests in many ways:

it('should emit event search_triggered', { retries: 1 }, () => {...}

it('should emit event search_triggered', { retries: { runMode: 1, openMode: 1} }, () => {...}.

//and in global cypress.json

{
  "retries": {
    "runMode": 1,
    "openMode": 3
  }
}

docker Image:

FROM cypress/browsers:node12.6.0-chrome77
#install cypress and dependecy
COPY e2e ./e2e
WORKDIR ./e2e
RUN npm ci
```

command use to run docker:

docker run --rm --ipc=host -m 4GB -e CYPRESS_VIDEO=false
–entrypoint=npm “…/cypress-test:5.5.0-1”
run testOnJenkins – --env configFile=“cypress-$ENVIRONMENT_ID”


Cypress:    5.5.0                                                                      
Browser:    Electron 85

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 19 (15 by maintainers)

Most upvoted comments

The slowdown can be attributed to this line https://github.com/cypress-io/cypress/blob/7d4e38e4c59440ad423bbf5893c9fa602fe46c2c/packages/server/lib/reporter.js#L146

The runnable is becoming larger and larger

bahmutov on Dec 17, 2020

@jennifer-shehane this was supposed to be the marquee feature of Cypress 5. I have a trivial example above that reproduces the hang, but it’s now been 10 days with no response and Cypress 6 coming out in that time. I love Cypress, but the pattern of lack of responsiveness to, let alone fixing of existing issues in the apparent rush to deliver new features is getting to be a real problem for us.

Likely this issue is very specific to the structure of the test code, perhaps the combination of hooks and suites, or the test code itself.

To be frank, as a professional tester I’m disappointed that literally the first thing I tried to reproduce the hang worked. I’m even more disappointed that the Cypress team didn’t even try something simple like this and instead made the assumption that it was an obscure edge case. To me, that suggests that new Cypress features aren’t really being subjected to more than shallow confirmatory testing, which for a testing tool is scary.

Sorry for the rant. Again, I’ve been using Cypress for a couple years now and it’s overall been a positive experience. I just haven’t known how best to voice my frustration with the seeming lack of support and not knowing which bug reports will just disappear into a black hole. Please take this as constructive feedback from a tester who would love to see Cypress become even better.

c32hedge on Nov 30, 2020

Likely this issue is very specific to the structure of the test code, perhaps the combination of hooks and suites, or the test code itself.

We don’t have anything to investigate until a reproducible example is provided. Here are some tips for providing a Short, Self Contained, Correct, Example and our own Troubleshooting Cypress guide.

jennifer-shehane on Nov 2, 2020