"Build Analysis" report is missing a build break in a test

[markples]

or perhaps the build break is being classified along with different known failures? Note that the build break is due to an analyzer.

I don't know if these links will persist so here are links + screenshots. This is the analysis: https://github.com/dotnet/runtime/pull/83895/checks?check_run_id=12264638203

And this is a failure:
https://github.com/dotnet/runtime/pull/83895/checks?check_run_id=12262235297

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

or perhaps the build break is being classified along with different known failures? Note that the build break is due to an analyzer.

I don't know if these links will persist so here are links + screenshots. This is the analysis: https://github.com/dotnet/runtime/pull/83895/checks?check_run_id=12264638203

And this is a failure:
https://github.com/dotnet/runtime/pull/83895/checks?check_run_id=12262235297

Author:	markples
Assignees:	-
Labels:	area-Infrastructure
Milestone:	8.0.0

[hoyosjs]

@missymessa @AlitzelMendez is there any chance you can check this? The second error doesn't really match the blob on #83655, but it's getting matched.

[hoyosjs]

@markples I fixed the issues. Now they actually surface.

[hoyosjs]

It doesn't explain the second issue matching, hence asking help from Ali

[AlitzelMendez]

At the moment that this build was analyzed, it matched the errors correctly.

The problem was on the regex for the issue: #83655

When this was analyzed the regex was:
"ErrorPattern": "['WasmTestOnBrowser.+ END OF WORK ITEM LOG: Command timed out, and was killed]" which was basically matching everything.

This was fixed two days ago:

but at that point this error probably matched a ton of builds, in fact if you see at the numbers from the last 7 days the number is unusually high (546 builds).

When the error is updated, we analyzed the builds from the last 24 hours, but this build wasn't part of that timeframe so we didn't reanalyze the build.

[hoyosjs]

Wow, thanks Ali :) it's hard to know where in time things happen sometimes. Appreciate the investigation.

[markples]

Thanks to both of you!