[VM] Coverage reports erroneously highlight @override

[matanlurey]

I'm less sure how to describe this one, so I guess an example is in order:

      43            0 :   @override
      44              :   int get _mask {
      45              :     // coverage:ignore-start
      46              :     assert(false, 'Should not be called; file a bug report!');
      47              :     return key._mask;
      48              :     // coverage:ignore-end
      49              :   }

[dart-github-bot]

Summary: Coverage reports incorrectly include @override annotations in the coverage calculation, leading to inaccurate coverage metrics. This occurs when @override annotations are present on methods that are marked as unreachable using // coverage:ignore-start and // coverage:ignore-end.

[a-siva]

@matanlurey if I understand correctly your question is why do we have coverage listed on line 43 instead of line 44 in the example above ?

[matanlurey]

Right sorry, the title of this issue is bad. Renamed