-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[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
[main] Update dependencies from dotnet/runtime #24985
Conversation
…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
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.
|
…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
@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
@kasperk81 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 |
@marcpopMSFT I see this failure a lot
which of the issues is tracking it? |
all commits that bot is updating right now dotnet/runtime@e3442b4...47d9c43 failing test:
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
@elinor-fung there are two new files for interop generator. is this expected? |
Thanks @kasperk81. Yes, those are expected new files for the interop generator. I pushed an update to the test. |
thanks!
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 |
That error should be resolved via #25049. |
cool. that is merged to main, so we need to just merge main in pr branch. |
actually target branch of #25049 was |
Yeah, we can probably cherry-pick the commit into main. cc/ @MackinnonBuck |
See: #25059 |
that pr is failing with reverse message:
you'd need to cherry-pick on this pr branch |
(cherry picked from commit 588aa53)
Cherry-picked 588aa53 & merged main. Hopefully that does the trick! |
This pull request updates the following dependencies
From https://github.com/dotnet/runtime