Repository navigation
Build analysis generates duplicate reports #11211
Description
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 |
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
Metadata
Metadata
Assignees
Labels
No labels
Activity
jkotas commentedon Oct 10, 2022
cc @markwilkie @missymessa
missymessa commentedon Oct 10, 2022
cc @ulisesh
ulisesh commentedon Oct 11, 2022
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 commentedon Jan 30, 2023
PR: https://dev.azure.com/dnceng/internal/_git/dotnet-helix-service/pullrequest/29270
ulisesh commentedon Feb 10, 2023
Validated with dotnet/runtime#35066 it should only test known issues but the error message is in the build logs too