-
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
[main] Update dependencies from dotnet/runtime #22892
[main] Update dependencies from dotnet/runtime #22892
Conversation
…1203.1 Microsoft.NETCore.Platforms , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.App.Runtime.win-x64 , System.CodeDom , System.Security.Cryptography.ProtectedData , System.Resources.Extensions , System.Reflection.MetadataLoadContext , Microsoft.NET.HostModel , Microsoft.Extensions.DependencyModel , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Ref , 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-alpha.1.21602.1 -> To Version 7.0.0-alpha.1.21603.1
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.
|
Build_DoesNotGenerateManifestJson_IncludesJSModulesOnBlazorBootJsonManifest and and JSModules_ManifestIncludesModuleTargetPaths are failing
@lewing is there someone who could take a look? I figured it might be a baseline update, but it looks like not. |
also some failures in Microsoft.DotNet.Watcher.Tools.NoDepsAppTests, and the similar failure in
@dotnet/domestic-cat is this familiar? |
@pavelsavara can you take a look |
I have problems downloading all the binaries necessary to build this repo right now, but I will continue first thing on Monday morning. |
It's the files The Blazor would put those files into If we want to leave them there here is change which could probably fix the tests. @lewing please advise. I don't know about |
|
This is a rough corner of how we build the runtime pack, I suspect the new files are probably just escaping a work around in the blazor sdk targets. We should fix that but I'd like to solve the underlying problem as well. |
…1203.8 Microsoft.NETCore.Platforms , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.App.Runtime.win-x64 , System.CodeDom , System.Security.Cryptography.ProtectedData , System.Resources.Extensions , System.Reflection.MetadataLoadContext , Microsoft.NET.HostModel , Microsoft.Extensions.DependencyModel , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Ref , 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-alpha.1.21602.1 -> To Version 7.0.0-alpha.1.21603.8
…1204.4 Microsoft.NETCore.Platforms , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.App.Runtime.win-x64 , System.CodeDom , System.Security.Cryptography.ProtectedData , System.Resources.Extensions , System.Reflection.MetadataLoadContext , Microsoft.NET.HostModel , Microsoft.Extensions.DependencyModel , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Ref , 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-alpha.1.21602.1 -> To Version 7.0.0-alpha.1.21604.4
…1206.1 Microsoft.NETCore.Platforms , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.App.Runtime.win-x64 , System.CodeDom , System.Security.Cryptography.ProtectedData , System.Resources.Extensions , System.Reflection.MetadataLoadContext , Microsoft.NET.HostModel , Microsoft.Extensions.DependencyModel , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Ref , 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-alpha.1.21602.1 -> To Version 7.0.0-alpha.1.21606.1
Thanks @lewing, I've created dotnet/aspnetcore#38844 to track this work. Just to confirm, is this PR currently blocked on us or can dotnet/aspnetcore#38844 be addressed in the new year once people return? cc/ @pavelsavara |
@TanayParikh this PR is blocked on these failures. Its your call whether we wait for the fix or you disable the tests for now. |
@danmoseley we'll be skipping the test soon. @TanayParikh will put out a PR now |
bab7dde should unblock this PR for now. Based on @pavelsavara's response #22892 (comment), this seems like expected failures in-light of additional files which aren't yet reflected in our static assets. Skipped the tests as this shouldn't break Blazor (but we will of course lose some coverage in that area until the tests can be re-enabled). I'll look into #22903 as it's not currently passing CI. dotnet/aspnetcore#38844 tracks the longer term fix. |
Thanks both! |
The (Note the AoT failures you may see are from a prior test run which is now passing after automatic retry). |
@MattGal is your Nuget retry work already enabled in this context? |
Sorry I don't see this error in the linked builds' attempt #1, can you point me at where you're copying that from? |
|
Ah in this case @danmoseley I can confirm none of these settings are set on a test machine, and probably should be (by the test). It's actually kind of amazing these tests are as reliable as they seem to be given that. I'll spend a few minutes scratching my head at how they're declared and may make some suggestions. |
Suggestion (doesn't have to be part of this PR): Go here:https://github.com/dotnet/sdk/blob/main/build/RunTestsOnHelix.sh Add something like :export NUGET_ENABLE_EXPERIMENTAL_HTTP_RETRY=true Go here:https://github.com/dotnet/sdk/blob/main/build/RunTestsOnHelix.cmd Add something like :set NUGET_ENABLE_EXPERIMENTAL_HTTP_RETRY=true |
@dotnet/domestic-cat are you OK with the edits suggested above ? (thanks @MattGal !) Context: these just cause Nuget to try harder in the face of network issues. They should not be relevant to whatever the tests are trying to verify. I believe NuGet expects to enable these flags by default in future, as well. |
Pushed those changes up. |
This pull request updates the following dependencies
From https://github.com/dotnet/runtime