v8 test coverage in jest is incorrect when upgrading to 20.10.0

Version

20.10.0

Platform

Macbook Pro M1/M2 / Ubuntu 22.04 x64 (GitHub runner)

Subsystem

V8

What steps will reproduce the bug?

See https://github.com/jestjs/jest/issues/14766

How often does it reproduce? Is there a required condition?

Found a consistent repro, but initially it was flaky because of the order jest was running tests.

What is the expected behavior? Why is that the expected behavior?

20.9.0 just works
20.10.0 fails

So this is a regression.

What do you see instead?

Coverage information is wrong in jest, unclear why, but based what we know Node is the place where this will most likely be fixed.

Additional information

Based on https://nodejs.org/en/blog/release/v20.10.0, cc @joyeecheung as you might be interested/know what's wrong.

Based on https://github.com/jestjs/jest/issues/14764, cc @kwmhp as you experienced the same problem as us, and figure out the version upgrade is what triggers it.

リンクされた Jest の再現ケースから始め、記載されている MacBook および Ubuntu プラットフォームで、Node 20.9.0 と 20.10.0 の間のカバレッジ動作を比較します。Node v20.10.0 のリリースノートを読み、リグレッションが Node 自体で再現するかどうかを確認します。完了の条件は、報告されたテスト順序の条件下でカバレッジ出力が正しいことです。