Andy Ayers

Any failure in a non-PR job is in some sense infrastructure failure or a pre-existing failure. The main thing that would be nice here is the ability to quickly see...

Thanks @ChadNedzlek How about for something like: https://dev.azure.com/dnceng/public/_build?definitionId=1000. For the recent runs one of the failures is in the `GetTotalPauseDuration` test. There is an open issue for this https://github.com/dotnet/runtime/issues/74877 --...

Likely the same as https://github.com/dotnet/runtime/issues/86006, but one that build analysis can latch on. I suspect there is some way to co-opt an existing issue and make it build analysis aware,...

Also https://github.com/dotnet/runtime/issues/85371 may be a dup.

The two recent appearances are from preliminary runs in PRs that had issues. So I would probably hold off looking at the crash dumps (if any).

Hard to say, I think codegen is a good a guess as any. Are all the crashes on osx-x64?

FYI @dotnet/jit-contrib A few large local regressions. The ones I looked at were all additional cloning in loops with type tests.

Hmm, rather bigger diffs than I was expecting. I will need to dig in and see if this is all attributable to more cloning, and whether it is time to...

Looks like regressions are indeed from more cloning.

In particular type test cloning is driven by the likelihood of the type test succeeding, and with this profile update we now see more tests that appear successful.