Skip to content

Conversation

@dotnet-maestro
Copy link
Contributor

@dotnet-maestro dotnet-maestro bot commented Sep 20, 2022

This pull request updates the following dependencies

From https://github.com/dotnet/runtime

  • Subscription: aa69f164-2492-460a-3914-08d8e9750bf8
  • Build: 20220925.4
  • Date Produced: September 26, 2022 10:02:33 AM UTC
  • Commit: b0920912512aa7e205363b046a1911e6a97df31f
  • Branch: refs/heads/main

…0919.17

Microsoft.DotNet.ILCompiler , Microsoft.Extensions.DependencyModel , Microsoft.NET.HostModel , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Ref , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.Platforms , System.CodeDom , System.Reflection.MetadataLoadContext , System.Resources.Extensions , System.Security.Cryptography.ProtectedData , System.Text.Encoding.CodePages , VS.Redist.Common.NetCore.SharedFramework.x64.8.0 , VS.Redist.Common.NetCore.TargetingPack.x64.8.0
 From Version 8.0.0-alpha.1.22468.3 -> To Version 8.0.0-alpha.1.22469.17
@ghost ghost added the Area-CodeFlow label Sep 20, 2022
@dotnet-maestro
Copy link
Contributor Author

Notification for subscribed users from https://github.com/dotnet/runtime:

@dnr-codeflow

Action requested: Please take a look at this failing automated dependency-flow pull request's checks; failures may be related to changes which originated in your repo.

  • This pull request contains changes from your source repo (https://github.com/dotnet/runtime) and seems to have failed checks in this PR. Please take a peek at the failures and comment if they seem relevant to your changes.
  • If you're being tagged in this comment it is due to an entry in the related Maestro Subscription of the Build Asset Registry. If you feel this entry has added your GitHub login or your GitHub team in error, please update the subscription to reflect this.
  • For more details, please read the Arcade Darc documentation

@kasperk81
Copy link
Contributor

@joperezr it needs 8bbfc5d

        CompilerServer: server failed - server rejected the request 'Exception during compilation: The method or operation is not implemented.' - 9cd2ee57-589c-4bc3-b611-515d7932ac75
      C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\Roslyn\Microsoft.CSharp.Core.targets(79,5): error :  [C:\h\w\BFF80A14\t\dotnetSdkTests\oannp0tq.zly\ItCanNewResto---C3AFA90D\ItCanNewResto---C3AFA90D.csproj]

@kasperk81
Copy link
Contributor

@joperezr it needs 8bbfc5d

#27803 (comment) it's a different version <MicrosoftNetCompilersToolsetVersion>4.3.0-3.22465.2</MicrosoftNetCompilersToolsetVersion>

@joperezr
Copy link
Member

Yes, in order to ingest dotnet/runtime the sdk repo now needs to either bump it's sdk to use 7.0 RC1, or use the Microsoft.NET.Compilers.Toolset package that shipped with RC1, which was 4.4.0-2.22426.8. Finally, the full framework legs are failing because they run some tests against an old MSBuild which is why they are failing, we just need to add an attribute to those tests so that they only run if we are using MSBuild 17.4.0-preview-22428-01+14c24b2d3 or greater.

I'll need to make these changes in the release/7.0.1xx-rc2 branch very soon, so once I have those I'll cherry-pick those changes here as well.

@kasperk81
Copy link
Contributor

arcade was updated to rc1, i don't see why dotnet/sdk can't use rc1 right away.

dotnet-maestro bot and others added 3 commits September 21, 2022 12:24
…0920.15

Microsoft.DotNet.ILCompiler , Microsoft.Extensions.DependencyModel , Microsoft.NET.HostModel , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Ref , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.Platforms , System.CodeDom , System.Reflection.MetadataLoadContext , System.Resources.Extensions , System.Security.Cryptography.ProtectedData , System.Text.Encoding.CodePages , VS.Redist.Common.NetCore.SharedFramework.x64.8.0 , VS.Redist.Common.NetCore.TargetingPack.x64.8.0
 From Version 8.0.0-alpha.1.22468.3 -> To Version 8.0.0-alpha.1.22470.15
…0921.15

Microsoft.DotNet.ILCompiler , Microsoft.Extensions.DependencyModel , Microsoft.NET.HostModel , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Ref , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.Platforms , System.CodeDom , System.Reflection.MetadataLoadContext , System.Resources.Extensions , System.Security.Cryptography.ProtectedData , System.Text.Encoding.CodePages , VS.Redist.Common.NetCore.SharedFramework.x64.8.0 , VS.Redist.Common.NetCore.TargetingPack.x64.8.0
 From Version 8.0.0-alpha.1.22468.3 -> To Version 8.0.0-alpha.1.22471.15
@marcpopMSFT
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@v-wuzhai
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

…0922.5

Microsoft.DotNet.ILCompiler , Microsoft.Extensions.DependencyModel , Microsoft.NET.HostModel , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Ref , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.Platforms , System.CodeDom , System.Reflection.MetadataLoadContext , System.Resources.Extensions , System.Security.Cryptography.ProtectedData , System.Text.Encoding.CodePages , VS.Redist.Common.NetCore.SharedFramework.x64.8.0 , VS.Redist.Common.NetCore.TargetingPack.x64.8.0
 From Version 8.0.0-alpha.1.22468.3 -> To Version 8.0.0-alpha.1.22472.5
@kasperk81
Copy link
Contributor

CompilerServer error was fixed. timeout is unrelated.
this is blocking dotnet/installer#14559

@joperezr
Copy link
Member

Before this gets merged though, seems like the commit I added here that redirects full framework runs to the Helix staging environment is overflowing that environment's capacity, so now we can't get those legs to finish in time for our release branches. @marcpopMSFT should we just temporarily disable the FullFramework legs (either here or release) while the Helix production environment gets the VS that we need (which ETA is mid-week next week)? Otherwise, I'm afraid we'll have a very hard time getting green CI's in either branch as it looks like staging environment's capacity is very limited.

…0924.1

Microsoft.DotNet.ILCompiler , Microsoft.Extensions.DependencyModel , Microsoft.NET.HostModel , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Ref , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.Platforms , System.CodeDom , System.Reflection.MetadataLoadContext , System.Resources.Extensions , System.Security.Cryptography.ProtectedData , System.Text.Encoding.CodePages , VS.Redist.Common.NetCore.SharedFramework.x64.8.0 , VS.Redist.Common.NetCore.TargetingPack.x64.8.0
 From Version 8.0.0-alpha.1.22468.3 -> To Version 8.0.0-alpha.1.22474.1
…0924.6

Microsoft.DotNet.ILCompiler , Microsoft.Extensions.DependencyModel , Microsoft.NET.HostModel , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Ref , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.Platforms , System.CodeDom , System.Reflection.MetadataLoadContext , System.Resources.Extensions , System.Security.Cryptography.ProtectedData , System.Text.Encoding.CodePages , VS.Redist.Common.NetCore.SharedFramework.x64.8.0 , VS.Redist.Common.NetCore.TargetingPack.x64.8.0
 From Version 8.0.0-alpha.1.22468.3 -> To Version 8.0.0-alpha.1.22474.6
…0925.4

Microsoft.DotNet.ILCompiler , Microsoft.Extensions.DependencyModel , Microsoft.NET.HostModel , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Ref , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.Platforms , System.CodeDom , System.Reflection.MetadataLoadContext , System.Resources.Extensions , System.Security.Cryptography.ProtectedData , System.Text.Encoding.CodePages , VS.Redist.Common.NetCore.SharedFramework.x64.8.0 , VS.Redist.Common.NetCore.TargetingPack.x64.8.0
 From Version 8.0.0-alpha.1.22468.3 -> To Version 8.0.0-alpha.1.22475.4
@marcpopMSFT
Copy link
Member

Looks like full framework passed the last few times. Is that because of lower flow over the weekend or something else? We need to figure out the Darwin leg failure though as that's showing up across multiple branches. Open to suggestions.

@joperezr
Copy link
Member

I'd imagine it is because of the lower flow. I'd expect that to also not be the case once this gets merged, since now all PRs against main would start queuing work into that staging queue. @dotnet/dnceng is that right for us to assume that queues in the staging helix environment have much less resources than prod?

@jonfortescue
Copy link
Contributor

@joperezr yep, that's correct, the staging environment does not scale up the way prod does.

@kasperk81
Copy link
Contributor

We need to figure out the Darwin

just did, darwin in staging are clogged and we only needed full framework to utilize staging, nothing else.
apply the suggestion to unblock this (which will unblock installer)

Co-authored-by: kasperk81 <83082615+kasperk81@users.noreply.github.com>
@marcpopMSFT marcpopMSFT merged commit 83a07d1 into main Sep 27, 2022
@marcpopMSFT marcpopMSFT deleted the darc-main-4987d474-261f-4de3-b862-1a25f52192fb branch September 27, 2022 01:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants