[Bug]: v8 coverage lowers when more tests are executed

[TWiStErRob]

[Bug]: v8 coverage lowers when more tests are executed

[kwmhp]

Hi
This seems to be the same problem as in my issue #14764
Have you tested this with Node 20.9.0?

[TWiStErRob]

Yep, confirmed 20.9.0 -> 20.10.0 causes it.

Raised nodejs/node#51251

[ritchieanesco]

+1 also getting code coverage failure after updating to 20.10.0.

[cenfun]

I found that comment following two lines in node_modules/collect-v8-coverage/index.js will fix it.

    //await this.postSession('Profiler.stopPreciseCoverage');

    //await this.postSession('Profiler.disable');

[ritchieanesco]

Verified that commenting out both lines fixes the issue.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[TWiStErRob]

Still an issue.

[emiwidknowit]

still an issue

[jeroenzwart]

Yep, confirmed 20.9.0 -> 20.10.0 causes it.

Raised nodejs/node#51251

Still a issue and same problem with the upgrade

[cenfun]

Seems it can be fixed with await this.postSession('Debugger.enable');
see https://github.com/SimenB/collect-v8-coverage/pull/235/files

[TatyanaVl]

This is still an issue. Is there any progress?

[kmccammon]

I posted this originally on: nodejs/node#51251

Reposting here in case it's helpful...

I have been facing the same issue: my coverage report was 100% with 20.9.0, but as of 20.10.0, it now reports less than 100% coverage and somewhat randomly flags lines not covered.

I noticed that I get the same coverage reporting flakiness with 18.20.2 (I initially saw this issue when my GitHub actions started to fail). Coverage works fine with 18.19.1.

So there seems to be a change between 18.19.1 and 18.20.0 that causes the issue as well as between 20.9.0 to 20.10.0.

This is now causing my GitHub CI/CD actions to fail since GitHub is using 18.20.2.

[TatyanaVl]

@kmccammon - we are facing exactly the same issue.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[TWiStErRob]

Can't call it closed stale without a triage...

[kmccammon]

Can't call it closed stale without a triage...

Agreed, I'm stuck on node version 18.19.1 until this coverage issue is resolved.

[TWiStErRob]

I think we can safely say this project is abandoned:
https://github.com/jestjs/jest/issues?q=is%3Aclosed+label%3A%22Needs+Triage%22+label%3AStale

A ton of them are auto-closed without a single comment.