Remove ARMv6 from all platformgroups, matching s390x #64535
Conversation
Turns out CoreCLR uses platformgroups a lot for managing extra pipelines, and ignores valid subsets for these pipelines. We should just... not try and get involved in platformgroups.
|
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
|
Thanks! Some pipelines run over the weekend or once a month (depending on their cron expression set in YAML file), so it’s not easy to detect what breaks if the job condition is relaxed. |
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsTurns out CoreCLR uses platformgroups a lot for managing extra pipelines, and ignores valid subsets for these pipelines. We should just... not try and get involved in platformgroups. Ref. https://dev.azure.com/dnceng/public/_build/results?buildId=1580540&view=logs&jobId=86b05f7f-a5b8-51f0-63db-a6d409e0da15&j=86b05f7f-a5b8-51f0-63db-a6d409e0da15
|
ghost
locked as resolved and limited conversation to collaborators
4 participants
Turns out CoreCLR uses platformgroups a lot for managing extra pipelines, and ignores valid subsets for these pipelines.
We should just... not try and get involved in platformgroups.
Ref. https://dev.azure.com/dnceng/public/_build/results?buildId=1580540&view=logs&jobId=86b05f7f-a5b8-51f0-63db-a6d409e0da15&j=86b05f7f-a5b8-51f0-63db-a6d409e0da15
Ref. #64267 (comment)