Skip to content

[main] Update dependencies from dotnet/runtime #24985

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

Merged
merged 8 commits into from
Apr 26, 2022

Conversation

dotnet-maestro[bot]
Copy link
Contributor

@dotnet-maestro dotnet-maestro bot commented Apr 21, 2022

This pull request updates the following dependencies

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

  • Subscription: aa69f164-2492-460a-3914-08d8e9750bf8
  • Build: 20220424.3
  • Date Produced: April 25, 2022 5:42:24 AM UTC
  • Commit: 47d9c43ab1f10a98a348a28b3fd7ed9c4d35328b
  • Branch: refs/heads/main

…0420.8

Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.Platforms , System.Reflection.MetadataLoadContext , System.Resources.Extensions , System.Text.Encoding.CodePages , System.Security.Cryptography.ProtectedData , System.CodeDom , Microsoft.NET.HostModel , Microsoft.Extensions.DependencyModel , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Ref , VS.Redist.Common.NetCore.TargetingPack.x64.7.0 , VS.Redist.Common.NetCore.SharedFramework.x64.7.0
 From Version 7.0.0-preview.4.22219.9 -> To Version 7.0.0-preview.5.22220.8
@ghost ghost added the Area-CodeFlow label Apr 21, 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

dotnet-maestro bot and others added 3 commits April 22, 2022 12:34
…0422.1

Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.Platforms , System.Reflection.MetadataLoadContext , System.Resources.Extensions , System.Text.Encoding.CodePages , System.Security.Cryptography.ProtectedData , System.CodeDom , Microsoft.NET.HostModel , Microsoft.Extensions.DependencyModel , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Ref , VS.Redist.Common.NetCore.TargetingPack.x64.7.0 , VS.Redist.Common.NetCore.SharedFramework.x64.7.0
 From Version 7.0.0-preview.4.22219.9 -> To Version 7.0.0-preview.5.22222.1
…0423.6

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

kasperk81 commented Apr 25, 2022

@marek-safar could you merge main branch again?

@mmitche, @marcpopMSFT, @danmoseley. i can only comment on what i have seen as an outsider. this is a request for action.

flaky tests has slowed down code flow. there is a 99% of chance that one or more checks will fail in dotnet-maestro PRs, then someone will manually rerun the check from portal to make it "look" green and merge. eveyone is interested in just getting their stuff through and nobody has time or interest to actually go ahead fix these tests. the success rate of this pipeline is under water: https://dev.azure.com/dnceng/public/_pipeline/analytics/stageawareoutcome?definitionId=136&contextType=build

these tests were flaky two years ago and they are flaky today. there has been enough reminders and notifications, and enough time has been wasted by people who can't do anything about it. best thing to do now, imo, is disable all flaky tests in sdk and installer repos to unblock auto code flow. when somebody will find time to fix the tests (maybe this year or the next or never), they should enable them back.

…0424.3

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

@kasperk81
CC @mmitche @marek-safar @danmoseley

You are right. We've gone from single digit test instability in the fall to low double digits in Jan to even higher now and that's not sustainable. The efforts to improve test stability includes the following items that I'm tracking. Let me know if you're aware of more improvements we can make or if anyone has capacity to help.

I went ahead and created an Epic to track this work: #25044

@marek-safar
Copy link
Contributor

@marcpopMSFT I see this failure a lot

Unhandled exception: System.UnauthorizedAccessException: Access to the path '/Users/helix-runner/.templateengine/dotnetcli/v7.0.100-ci' is denied.
 ---> System.IO.IOException: Permission denied
   --- End of inner exception stack trace ---
   at System.IO.FileSystem.CreateDirectory(String fullPath)
   at System.IO.Directory.CreateDirectory(String path)
   at Microsoft.TemplateEngine.Utils.PhysicalFileSystem.CreateDirectory(String path)
   at Microsoft.TemplateEngine.Edge.EngineEnvironmentSettings..ctor(ITemplateEngineHost host, Boolean virtualizeSettings, String settingsLocation, IEnvironment environment, IComponentManager componentManager, IPathInfo pathInfo)
   at Microsoft.TemplateEngine.Cli.Commands.BaseCommand.CreateEnvironmentSettings(GlobalArgs args, ParseResult parseResult)
   at Microsoft.TemplateEngine.Cli.Commands.BaseCommand`1.InvokeAsync(InvocationContext context)
   at Microsoft.TemplateEngine.Cli.Commands.BaseCommand`1.Invoke(InvocationContext context)

which of the issues is tracking it?

@kasperk81
Copy link
Contributor

all commits that bot is updating right now dotnet/runtime@e3442b4...47d9c43

failing test:

Microsoft.NET.Build.Tests.GivenThatWeWantToUseAnalyzers.It_resolves_analyzers_correctly(language: "C#", testAssetName: "AppWithLibrary") [FAIL]
Expected collection

{(Microsoft.NET.Sdk, , analyzers/Microsoft.CodeAnalysis.CSharp.NetAnalyzers.dll), (Microsoft.NET.Sdk, , analyzers/Microsoft.CodeAnalysis.NetAnalyzers.dll), (microsoft.codequality.analyzers, 2.6.0, analyzers/dotnet/cs/Microsoft.CodeQuality.Analyzers.dll), (microsoft.codequality.analyzers, 2.6.0, analyzers/dotnet/cs/Microsoft.CodeQuality.CSharp.Analyzers.dll), (microsoft.dependencyvalidation.analyzers, 0.9.0, analyzers/dotnet/Microsoft.DependencyValidation.Analyzers.dll), (microsoft.netcore.app.ref, , analyzers/dotnet/Microsoft.Interop.LibraryImportGenerator.dll), (microsoft.netcore.app.ref, , analyzers/dotnet/Microsoft.Interop.SourceGeneration.dll), (microsoft.netcore.app.ref, , analyzers/dotnet/cs/System.Text.Json.SourceGeneration.dll), (microsoft.netcore.app.ref, , analyzers/dotnet/cs/System.Text.RegularExpressions.Generator.dll)}

to be equivalent to

{(Microsoft.NET.Sdk, , analyzers/Microsoft.CodeAnalysis.CSharp.NetAnalyzers.dll), (Microsoft.NET.Sdk, , analyzers/Microsoft.CodeAnalysis.NetAnalyzers.dll), (microsoft.netcore.app.ref, , analyzers/dotnet/cs/System.Text.Json.SourceGeneration.dll), (microsoft.netcore.app.ref, , analyzers/dotnet/cs/System.Text.RegularExpressions.Generator.dll), (microsoft.codequality.analyzers, 2.6.0, analyzers/dotnet/cs/Microsoft.CodeQuality.Analyzers.dll), (microsoft.codequality.analyzers, 2.6.0, analyzers/dotnet/cs/Microsoft.CodeQuality.CSharp.Analyzers.dll), (microsoft.dependencyvalidation.analyzers, 0.9.0, analyzers/dotnet/Microsoft.DependencyValidation.Analyzers.dll)}

but it contains too many items.

is due to dotnet/runtime@677f6e5.

needs this line

                        ("microsoft.netcore.app.ref", (string)null, "analyzers/dotnet/Microsoft.Interop.LibraryImportGenerator.dll"),
                        ("microsoft.netcore.app.ref", (string)null, "analyzers/dotnet/Microsoft.Interop.SourceGeneration.dll"),

after

("microsoft.dependencyvalidation.analyzers", "0.9.0", "analyzers/dotnet/Microsoft.DependencyValidation.Analyzers.dll")

@elinor-fung there are two new files for interop generator. is this expected?

@elinor-fung
Copy link
Member

Thanks @kasperk81. Yes, those are expected new files for the interop generator. I pushed an update to the test.

@kasperk81
Copy link
Contributor

kasperk81 commented Apr 25, 2022

thanks!
next up:

Microsoft.NET.Sdk.BlazorWebAssembly.Tests.WasmJsModulesIntegrationTests.Build_DoesNotGenerateManifestJson_IncludesJSModulesOnBlazorBootJsonManifest [FAIL]
      Expected subject to be a collection with 404 item(s), but found 406.

it happened at least once before: #22892 (comment)

cc @TanayParikh, @pavelsavara i think it is blocked on #25045, which in turn is blocked on #24971. not to mention this pr will presumeably unblock dotnet/installer#13659 (i.e. the first daily build of dotnet sdk with NativeAOT support)

@TanayParikh
Copy link
Contributor

That error should be resolved via #25049.

@kasperk81
Copy link
Contributor

cool. that is merged to main, so we need to just merge main in pr branch.

@kasperk81
Copy link
Contributor

actually target branch of #25049 wasdarc-release/7.0.1xx-preview4-bd2fbb86-407c-4281-9017-a5e5e5ed4cdb. so it needs more work to get that to main?

@TanayParikh
Copy link
Contributor

actually target branch of #25049 wasdarc-release/7.0.1xx-preview4-bd2fbb86-407c-4281-9017-a5e5e5ed4cdb. so it needs more work to get that to main?

Yeah, we can probably cherry-pick the commit into main. cc/ @MackinnonBuck

@MackinnonBuck
Copy link
Member

See: #25059

@kasperk81
Copy link
Contributor

See: #25059

that pr is failing with reverse message:

Microsoft.NET.Sdk.BlazorWebAssembly.Tests.WasmJsModulesIntegrationTests.Build_DoesNotGenerateManifestJson_IncludesJSModulesOnBlazorBootJsonManifest [FAIL]
      Expected subject to be a collection with 406 item(s), but found 404.

you'd need to cherry-pick on this pr branch darc-main-218d1a76-5a57-457c-b606-c7f1898b4911 otherwise if you force merge it, it will block the main branch and the prs targetting main until this pr is merged (there maybe more failures to fix here so it can get delayed). please also merge main to this pr in the same step.

@TanayParikh
Copy link
Contributor

Cherry-picked 588aa53 & merged main. Hopefully that does the trick!

@dotnet-maestro dotnet-maestro bot merged commit 033dcbc into main Apr 26, 2022
@dotnet-maestro dotnet-maestro bot deleted the darc-main-218d1a76-5a57-457c-b606-c7f1898b4911 branch April 26, 2022 07:42
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