Ricardo Arenas

Reopened. This is still an issue as the official build for #10749 failed with the same error. We're getting reports of repos being blocked in their 5.0 branches due to...

I'm retrying the build but I have little hope of it fixing things. Yep definitely not a matter of getting an older build machine. This is just still broken.

We expect https://github.com/dotnet/arcade/pull/10864 to fix this

It didn't: https://dev.azure.com/dnceng/internal/_build/results?buildId=1994663&view=logs&j=226748d0-f812-5437-d3f0-2dd291f5666e&t=bad11196-972e-5d03-45a8-9db526506073

taking a look.

Been running some experiments here, and my latest find is that the build agents don't seem to know that they have .net 6 installed. A call to `dotnet --list-sdks` is...

We, on purpose, only install the 6.0 runtime in the build machines, which helps with running darc after installing it, but in order to install darc, we'll need to also...

I was finally able to unblock both branches and trigger the subscriptions for both .net 3 and .net 5 eng channels. The 5.0 build needed a lot of attention. Remaining...

Changes to the runtime artifact are in. I will test the removal of the workarounds by targeting the staging pool provider that should have the updated image tomorrow.

The changes have been rolled out, but when trying to remove some of the workarounds, especially the ones in the validate stages of arcade, we still end up with a...