-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[release/7.0.1xx] Update dependencies from dotnet/runtime #27803
[release/7.0.1xx] Update dependencies from dotnet/runtime #27803
Conversation
…0909.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.7.0 , VS.Redist.Common.NetCore.TargetingPack.x64.7.0 From Version 7.0.0-rc.2.22459.1 -> To Version 7.0.0-rc.2.22459.6
…0909.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.7.0 , VS.Redist.Common.NetCore.TargetingPack.x64.7.0 From Version 7.0.0-rc.2.22459.1 -> To Version 7.0.0-rc.2.22459.15
…0910.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.7.0 , VS.Redist.Common.NetCore.TargetingPack.x64.7.0 From Version 7.0.0-rc.2.22459.1 -> To Version 7.0.0-rc.2.22460.1
|
This looks like it might be related to the Roslyn bump, @joperezr ? |
Would be great to have this unblocked so we can have an rc2 installer before the branch |
Yes this is due to the roslyn bump on runtime, particularly on the source generators, and also due to the fact that the sdk repo doesn't build with a recent enough roslyn when compared to those source generators. I've pushed a change that is bumping the roslyn version on the sdk which should resolve this issue. |
Seems like even after updating the version of Roslyn used by the repo some full framework tests are failing. After taking a look seems like that is because those tests are invoking VS csc.exe, and it seems like the version it is invoking does not yet have the fix for dotnet/roslyn#63318 . @jaredpar do we know if there is some VS version that has already picked up a csc that has that fix? @marcpopMSFT in case the answer for my previous question is no, would it be possible to disable those tests in full framework until we get a csc.exe with the fix in order to unblock the ingestion of dotnet/runtime into the sdk? For reference, this is happening since dotnet/runtime has some new generators which depend on a recent version of csc.exe that must have the fix for dotnet/roslyn#63318, and seems like the VS version we use to test in arcade doesn't have that. |
@joperezr looks like dotnet/roslyn@5d37065 isn't in a release yet. Even if it was, I think those tests run against released VS on a slight lag so it might not be feasible to wait. One option would be to use |
dotnet/runtime#75490 rolls back the roslyn bump |
…0912.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.7.0 , VS.Redist.Common.NetCore.TargetingPack.x64.7.0 From Version 7.0.0-rc.2.22459.1 -> To Version 7.0.0-rc.2.22462.6
Merged. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
As FYI, this PR doesn't have the rollback yet. There is an ongoing internal build and once it finishes successfully, this PR will be automatically updated and p ick it up, which should fix the CI failures |
…0913.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.7.0 , VS.Redist.Common.NetCore.TargetingPack.x64.7.0 From Version 7.0.0-rc.2.22459.1 -> To Version 7.0.0-rc.2.22463.4
a new build has finally made it |
after dotnet/runtime#75717, main is blocked by CompilerServer error: #28032. should we bump roslyn or use RequiresMSBuildVersionFact workaround @rainersigwald suggested above #27803 (comment)? backport of dotnet/runtime#75717 to 7.0 is also in progress. we will be in the same situation in release/7.0.1xx again |
Do we have a link to the build failure? A binlog we can look at? etc ... |
@jaredpar at the bottom of logs https://helix.dot.net/api/2019-06-17/jobs/4e8f20ce-2c1b-4e43-99a2-e6d190c5f1a0/workitems/EndToEnd.Tests.dll/console there are helix instructions about dump:
|
That is the following bug This will be in the next release of VS and .NET SDK. The fix got merged into servicing last night. Packages should be available this morning that we can use in the build to unblock this. |
To work around this:
That will pick up the patched toolset that has the fix for this problem. |
If we haven't made the change yet we should use version 4.4.0-3.22470.1 instead. |
This pull request updates the following dependencies
From https://github.com/dotnet/runtime