Tagging subscribers to this area: @directhex, @matouskozak
See info in area-owners.md if you want to be subscribed.

/azp run runtime-extra-platforms

@matouskozak can you please look at the CI failures? There are several without a linked issue, so they must be new/related to this PR.

Friendly reminder that Code Complete for the October Release is September 9. If we want this fix to be included in that release, please merge this PR before that date.

@matouskozak can you please look at the CI failures? There are several without a linked issue, so they must be new/related to this PR.

Friendly reminder that Code Complete for the October Release is September 9. If we want this fix to be included in that release, please merge this PR before that date.

The BuildAnalysis checks runtime-extra-platforms on servicing branches? I thought only runtime pipeline is checked for BA to be green.

I'll go over them and link the issues.

I think BA does check runtime-extra-platforms, but in release branches, the BuildAnalysis check will always show as failed to ensure the PR submitters look at their failures and confirm they are all indeed unrelated (we want to minimize risk).

Sorry that my change broke Android!

No problem @richlander.

Looking at the failures related to this PR, this change only affected android-x64 and linux-bionic-x64 jobs of which all of them are green (previously failing). Did a quick check and the "other" failures are also seen on rolling-builds of release/8.0-staging https://dev.azure.com/dnceng-public/public/_build/results?buildId=799223. I think it is good to merge @carlossanlop.

/ba-g the runtime-extra-platforms are unrelated as they are occurring on different than android-x64 jobs and are also present on rolling-builds