[master] Update dependencies from dotnet/runtime

[dotnet-maestro]

This pull request updates the following dependencies

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

• Subscription: ea219f43-0754-4d2f-576e-08d76e1d56cb
• Build: 20201101.7
• Date Produced: 11/2/2020 6:26 AM
• Commit: ecd979c9860caee8326f8678736ae98a77bdae5b
• Branch: refs/heads/master

• Updates:
  • System.CodeDom: from 6.0.0-alpha.1.20551.1 to 6.0.0-alpha.1.20551.7
  • Microsoft.NET.HostModel: from 6.0.0-alpha.1.20551.1 to 6.0.0-alpha.1.20551.7
  • Microsoft.Extensions.DependencyModel: from 6.0.0-alpha.1.20551.1 to 6.0.0-alpha.1.20551.7
  • Microsoft.NETCore.App.Runtime.win-x64: from 6.0.0-alpha.1.20551.1 to 6.0.0-alpha.1.20551.7
  • Microsoft.NETCore.DotNetHostResolver: from 6.0.0-alpha.1.20551.1 to 6.0.0-alpha.1.20551.7
  • Microsoft.NETCore.Platforms: from 6.0.0-alpha.1.20551.1 to 6.0.0-alpha.1.20551.7
  • Microsoft.NETCore.App.Internal: from 6.0.0-alpha.1.20551.1 to 6.0.0-alpha.1.20551.7
  • Microsoft.NETCore.App.Ref: from 6.0.0-alpha.1.20551.1 to 6.0.0-alpha.1.20551.7
  • Microsoft.NETCore.App.Host.win-x64: from 6.0.0-alpha.1.20551.1 to 6.0.0-alpha.1.20551.7
  • System.Resources.Extensions: from 6.0.0-alpha.1.20551.1 to 6.0.0-alpha.1.20551.7
  • System.Security.Cryptography.ProtectedData: from 6.0.0-alpha.1.20551.1 to 6.0.0-alpha.1.20551.7
  • System.Text.Encoding.CodePages: from 6.0.0-alpha.1.20551.1 to 6.0.0-alpha.1.20551.7

Coherency Updates

The following updates ensure that dependencies with a CoherentParentDependency
attribute were produced in a build used as input to the parent dependency's build.
See Dependency Description Format

• Coherency Updates:
  • Microsoft.NET.ILLink.Tasks: from 6.0.0-alpha.1.20516.1 to 6.0.0-alpha.1.20527.2 (parent: Microsoft.NETCore.App.Internal)

[AntonLapounov]

There is the following failure:

Microsoft.NET.Publish.Tests.GivenThatWeWantToRunILLink.ILLink_verify_analysis_warnings_hello_world_app(targetFramework: \"net5.0\")
The execution of a hello world app generated a diff in the number of warnings the app produces

This is a list of missing linker warnings generated with your change using a console app, if you are working on make things linker friendly please also submit a PR deleting these warnings:
-  ILLink : Trim analysis warning IL2070: System.RuntimeType.GetMethodBase(RuntimeType,RuntimeMethodHandleInternal
-  ILLink : Trim analysis warning IL2026: System.Reflection.CustomAttribute.GetAttributeUsage(RuntimeType
-  ILLink : Trim analysis warning IL2065: System.Reflection.CustomAttribute.AddCustomAttributes(ListBuilder`1&,RuntimeModule,Int32,RuntimeType,Boolean,RuntimeType.ListBuilder<Object>
-  ILLink : Trim analysis warning IL2055: System.Reflection.Emit.TypeBuilderInstantiation.Substitute(Type[]
-  ILLink : Trim analysis warning IL2026: System.Reflection.CustomAttribute.FilterCustomAttributeRecord(MetadataToken,MetadataImport&,RuntimeModule,MetadataToken,RuntimeType,Boolean,ListBuilder`1&,RuntimeType&,IRuntimeMethodInfo&,Boolean&
-  ILLink : Trim analysis warning IL2075: System.Reflection.CustomAttributeData.CustomAttributeData(RuntimeModule,MetadataToken,ConstArray&
-  ILLink : Trim analysis warning IL2055: System.Reflection.SignatureTypeExtensions.TryMakeGenericType(Type,Type[]
-  ILLink : Trim analysis warning IL2026: System.Reflection.Associates.AssignAssociates(Int32,RuntimeType,RuntimeType

Expected: True
Actual:   False
   at Microsoft.NET.Publish.Tests.GivenThatWeWantToRunILLink.ILLink_verify_analysis_warnings_hello_world_app(String targetFramework) in /_/src/Tests/Microsoft.NET.Publish.Tests/GivenThatWeWantToRunILLink.cs:line 384

and also Microsoft.NET.Build.Tests.GivenThatWeWantToBuildAnAppWithoutTransitiveProjectRefs.It_builds_the_project_successfully_when_RAR_finds_all_references test failed with STATUS_HEAP_CORRUPTION (-1073740940), which is probably intermittent.

[mangod9]

@wli3 is there an ETA for getting the latest runtime+asp.net dependencies propagated to sdk? We are looking at supported macos arm64 targets and support for that is included in the runtime. Thx!

[wli3]

@mangod9 runtime, asp.net owners their flow to SDK in the end. Although @joeloff do you have an estimation from our side?

[joeloff]

Nothing yet, I need to check to see if we have a new installer build ready to insert that contains the 6.0 changes Daniel made.

[mangod9]

runtime, asp.net owners their flow to SDK in the end

Ok, thanks. Will check who manages this for runtime. @joeloff does the sdk have a dependency on the installer? I thought it was the other way -- installer will be ready once sdk has consumed the runtime packages.

[wli3]

@vitek-karas @tlakollo could you fix the failing test? https://dev.azure.com/dnceng/public/_build/results?buildId=873483&view=ms.vss-test-web.build-test-results-tab&runId=27947008&resultId=100113&paneView=debug

[vitek-karas]

That is caused by my dotnet/runtime#43594 - I'll update the test.