-
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 #16425
[main] Update dependencies from dotnet/runtime #16425
Conversation
…0318.9 Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.Platforms , Microsoft.NET.HostModel , Microsoft.Extensions.DependencyModel , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Ref , System.Reflection.MetadataLoadContext , System.Resources.Extensions , System.CodeDom , System.Security.Cryptography.ProtectedData , VS.Redist.Common.NetCore.SharedFramework.x64.6.0 , System.Text.Encoding.CodePages From Version 6.0.0-preview.3.21167.1 -> To Version 6.0.0-preview.3.21168.9
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
I removed ios from the standard list as asking everyone to make Process conditional is a pretty bad breaking change. |
@marek-safar looks like we're getting the same error after the change. It might be because iOS is still marked as a supported platform in the build we're using for stage 0. |
yep, I think that's the case but not sure how to skip that |
You might have to make that change to remove iOS from supported platforms as a separate PR, get it to flow through and produce a build, then use that build as stage 0 here. It would take a day or two but I'm not sure how to get a passing build otherwise. |
Is it only Process.Start? If so another option could be to remove @marek-safar are you taking care of this? |
That's not an option.
I'd like to hear from @jeffhandley or @terrajobst as they own the spec which includes ios everywhere. |
…0319.6 Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.DotNetHostResolver , Microsoft.NETCore.Platforms , Microsoft.NET.HostModel , Microsoft.Extensions.DependencyModel , Microsoft.NETCore.App.Host.win-x64 , Microsoft.NETCore.App.Ref , System.Reflection.MetadataLoadContext , System.Resources.Extensions , System.CodeDom , System.Security.Cryptography.ProtectedData , VS.Redist.Common.NetCore.SharedFramework.x64.6.0 , System.Text.Encoding.CodePages From Version 6.0.0-preview.3.21167.1 -> To Version 6.0.0-preview.3.21169.6
The other way to get a passing build here will be to update <ItemGroup>
<SupportedPlatform Remove="iOS" />
<SupportedPlatform Remove="Android" />
</ItemGroup> I expect that would get the build unblocked here, but we also need to reconsider whether or not it makes sense for Edit: Changed from |
The failures I'm now seeing (so far) are the following:
|
Two tests end up with the same output directory again.
hmm |
@wli3 this is because your fix 2638bba which added
updated this caller to add that filename
but not these callers How do you want to fix this? |
Options
what do you prefer? I suggest option 3. |
@sfoslund could you help work on this since you are the domestic cat this week? I think we can just take approach give up on trying to encode every test to a deterministic test path. The structure of the tests makes this too complicated. Instead just use random bytes . But make sure the test will print out the temp folder as part of the output. So we can debug it later. |
Sure, I created an issue to track since there's no need to block on this: #16490 |
It looks like there is issue dotnet/installer#10013 related to this which fails all WinForms/WPF apps using latest 6.0.100-preview.3.21173.8 SDK, if anyone knows when the issue dotnet/installer#10013 will be fixed? |
This pull request updates the following dependencies
From https://github.com/dotnet/runtime