Build analysis generates duplicate reports

[jkotas]

The tables with hit statistics included in issues are duplicated. It is regression introduced in last few days.

Example from dotnet/runtime#76826:

Report

Build	Definition	Step Name	Console log	Pull Request
45431	dotnet/runtime	Send to Helix	Log	dotnet/runtime#76764
45701	dotnet/runtime	Send to Helix	Log	dotnet/runtime#76799

Build	Definition	Test	Pull Request
45431	dotnet/runtime	LibraryImportGenerator.UnitTests.IncrementalGenerationTests.GeneratorRun_WithNewCompilation_DoesNotKeepOldCompilationAlive	dotnet/runtime#76764
45701	dotnet/runtime	LibraryImportGenerator.UnitTests.IncrementalGenerationTests.GeneratorRun_WithNewCompilation_DoesNotKeepOldCompilationAlive	dotnet/runtime#76799

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
4	4	4

Release Note Category

• Feature changes/additions
• Bug fixes
• Internal Infrastructure Improvements

Release Note Description

Remove duplicated Known Issues matches from issue report

[jkotas]

cc @markwilkie @missymessa

[missymessa]

cc @ulisesh

[ulisesh]

This happens because we find the error message in both the build and test logs so we report the match twice. This is something we can prevent by not excluding test matches from the build report

[ulisesh]

PR: https://dev.azure.com/dnceng/internal/_git/dotnet-helix-service/pullrequest/29270

[ulisesh]

Validated with dotnet/runtime#35066 it should only test known issues but the error message is in the build logs too