-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[main] Update dependencies from dotnet/runtime #28032
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[main] Update dependencies from dotnet/runtime #28032
Conversation
…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
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.
|
|
|
#27803 (comment) it's a different version |
|
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 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. |
|
arcade was updated to rc1, i don't see why dotnet/sdk can't use rc1 right away. |
…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
…onment which has VS 17.4 P2.1 installed
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
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
|
CompilerServer error was fixed. timeout is unrelated. |
|
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
|
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. |
|
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? |
|
@joperezr yep, that's correct, the staging environment does not scale up the way prod does. |
just did, darwin in staging are clogged and we only needed full framework to utilize staging, nothing else. |
Co-authored-by: kasperk81 <83082615+kasperk81@users.noreply.github.com>
This pull request updates the following dependencies
From https://github.com/dotnet/runtime