[release/7.0] Don't try to build PGO tools on platforms with no CoreCLR port. #75003
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsBackport of #74147 to release/7.0 /cc @directhex Customer ImpactTestingRiskIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
jeffschwMSFT
added
area-Infrastructure-mono
and removed
area-Infrastructure-libraries
labels
|
Tagging subscribers to this area: @directhex Issue DetailsBackport of #74147 to release/7.0 /cc @directhex Customer ImpactTestingRiskIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
|
Re-running the failed CI legs. They were a known, unrelated issue that has already been mitigated. (the max limit of runs was exceeded). |
|
@mdh1418 or @akoeplinger can we get a code review sign off? Edit: @marek-safar please approve this backport. |
ghost
locked as resolved and limited conversation to collaborators
Backport of #74147 to release/7.0
/cc @directhex
Customer Impact
This should only impact customer-supported platforms like s390x and ppc64le, and the backport is by request of the community.
Testing
Customer indicates that the PR in question works for them. CI is fine otherwise on our side.
Risk
Should not impact any of our scenarios.