Code coverage failing on PRs

[sidharthv96]

The github workflow for coverage running on node 12 - ubuntu is consistently failing across PRs.

[sidharthv96]

@sosukesuzuki You are also facing the same issue right?

[sosukesuzuki]

@sidharthv96 yes, the action seems to fail if the test takes a long time to run. This is a problem, but unfortunately we will have to ignore it for now.

/cc @thorn0 @fisker Do you have a solution for this?

[sidharthv96]

Seems like coverage isn't generated at all.

[fisker]

Not sure how to fix it.

@sidharthv96 Is this from github actions job?

[sidharthv96]

@fisker No, that was from my local.

==> Detecting git/mercurial file structure
==> Reading reports
    - Skipping empty file ./coverage/lcov.info
--> No coverage data found.
    Please visit http://docs.codecov.io/docs/supported-languages
    search for your projects language to learn how to collect reports.

This is from actions.

I'm checking why jest stopped picking up the coverage. Do you know any recent commits that might've caused the issue?

[fisker]

Local test don't collect coverage by default, you can run yarn test --collectCoverage.

[fisker]

Seems it stopped collect coverage from jest upgrade commit.

[sidharthv96]

I used ENABLE_CODE_COVERAGE flag.
Yeah, downgraded jest and running test now.

[sidharthv96]

@fisker Tried downgrading to 25.1.0 and ran tests with yarn test --collectCoverage. Still no coverage locally.

#7894 will help test the CI

[sidharthv96]

Any chance there is a mock fs?

When using mock-fs make sure to run mock.restore() when your tests are done running, or else the reports wont get generated on the CI.

[SimenB]

This is a bug in Jest, fix here: jestjs/jest#9724. I'll release a patch sometime today.

"resolutions": {
  "@jest/transform": "25.1.0"
}

in package.json works in the meantime, or just reverting the upgrade for now.

[SimenB]

Patch out: https://github.com/facebook/jest/releases/tag/v25.2.4

[thorn0]

closed by #7901