Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Report timing out despite having `coverage`

See original GitHub issue

Hi,

For some reason, with cypress run or cypress open can be set even when only visiting a page to ensure coverage on the server end), I’m getting the error:

CypressError: cy.task('coverageReport') timed out after waiting 60000ms.

Because this error occurred during a 'after all' hook we are skipping all of the remaining tests.

I’m getting the following debugging output before the error.

  code-coverage parsed sent coverage +0ms
  code-coverage wrote coverage file /Users/brett/node-login/.nyc_output/out.json +1ms

  code-coverage parsed sent coverage +150ms
  code-coverage wrote coverage file /Users/brett/node-login/.nyc_output/out.json +2ms
  code-coverage saving coverage report using command: "nyc report --report-dir ./coverage --temp-dir /Users/brett/node-login/.nyc_output --reporter=text --reporter=html --reporter=lcov" +29ms
  code-coverage current working directory is /Users/brett/node-login +0ms

(Then the timeout occurs.)

I’ve added a mostly empty placeholder script file–with just a console.log statement even for those files which are only intended to be loaded to trigger server coverage, and I’ve confirmed that after instrumenting, this instrumented file is being loaded and that __coverage__ is set within it, but I’m still getting the above error.

Is there anything else I should be looking for besides an absent __coverage__?