Conversation
Forgind
left a comment
There was a problem hiding this comment.
I think this is reasonable both because it will save Microsoft a good amount of resources and because it will save time with waiting to rerun things. Not a strong preference though since selfishly, this makes it harder for me to try to fix it 🙂
|
If the Linux x64 job fails again because of API rate limit stuff, I'm just gonna merge on red. |
|
/backport to release/10.0.1xx-preview1 |
|
Started backporting to release/10.0.1xx-preview1: https://github.com/dotnet/sdk/actions/runs/13080512775 |
|
/backport to main |
|
Started backporting to main: https://github.com/dotnet/sdk/actions/runs/13080516392 |
|
/backport to release/9.0.2xx |
|
/backport to release/9.0.3xx |
|
Started backporting to release/9.0.2xx: https://github.com/dotnet/sdk/actions/runs/13185925034 |
|
Started backporting to release/9.0.3xx: https://github.com/dotnet/sdk/actions/runs/13185926733 |
|
@MiYanni an error occurred while backporting to "release/9.0.3xx", please check the run log for details! Validation Failed: {"resource":"PullRequest","code":"custom","message":"No commits between release/9.0.3xx and backport/pr-46435-to-release/9.0.3xx"} |
Related: https://teams.microsoft.com/l/message/19:2db9948434504972b9bc70d3b3ad71e2@thread.skype/1733772847082?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=4ba7372f-2799-4677-89f0-7a1aaea3706c&parentMessageId=1733772847082&teamName=.NET%20Developer%20Experience&channelName=CLI&createdTime=1733772847082
Summary
The ARM64 job has been consistently failing. While this is being investigated, I've added a flag that enables/disables this job. By default, it is set to
false. While this problem is being investigated, anyone doing investigations can either run the branch manually and check the checkbox to enable the job, or in their branch, set the default for this parameter totrue.I will backport these to other branches as those branches become no longer in lockdown.