Current the perf pipelines depends on OOBs being present in the testhost folder instead of being acquired app-local (which represents the customer scenario). We are removing OOBs from the testhost with https://github.com/dotnet/runtime/pull/35606.
I added a workaround to manually copy the runtime directory's content which includes OOBs into the testhost. This is a hack and should be fixed i.e. by including the built packages (e.g. System.Drawing.Common) into the payload and then restoring from that cache. I don't have enough context how the perf pipeline works but I assume, as I saw that the whole dotnet/performance repository is part of the correlation payload, that the performance library isn't prebuilt.
Current the perf pipelines depends on OOBs being present in the testhost folder instead of being acquired app-local (which represents the customer scenario). We are removing OOBs from the testhost with https://github.com/dotnet/runtime/pull/35606.
I added a workaround to manually copy the runtime directory's content which includes OOBs into the testhost. This is a hack and should be fixed i.e. by including the built packages (e.g. System.Drawing.Common) into the payload and then restoring from that cache. I don't have enough context how the perf pipeline works but I assume, as I saw that the whole dotnet/performance repository is part of the correlation payload, that the performance library isn't prebuilt.
cc @adamsitnik @DrewScoggins @safern