-
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
[release/7.0.1xx] Update dependencies from dotnet/arcade #28591
[release/7.0.1xx] Update dependencies from dotnet/arcade #28591
Conversation
…013.4 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions From Version 7.0.0-beta.22464.4 -> To Version 7.0.0-beta.22513.4
@dotnet/aspnet-blazor-eng as there are a bunch of Blazor test failures |
Taking a look. |
also, expected:
got
Doesn't look like it's doing the proper version interpolation. |
is reporting Just re-running the baselines results in an update of It's unclear why the test assembly's cc/ @marcpopMSFT @javiercn ideas or thoughts on why this may be? dotnet --info
|
Can you clarify which is the incorrect value? In the SDK repo we've updated to a stable branding. In this PR, we're updating the stage 0 SDK to be the RC2 version though. Could that be the issue (ie the stable version we're building versus the unstable one we're using to build)? |
Ahh okay, yeah I think that's it. cc/ @javiercn in case he can share any context on potentially running into this issue in previous releases. |
cc/ @javiercn if you can share any context you may have on the above. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Any luck here? Looks like still a lot of Blazor test failures on the latest run. |
@javiercn can you please comment on the above? |
There is a regression in normalizing the TargetPlatformVersion which is causing the It_succeeds_if_windows_target_platform_version_does_not_have_trailing_zeros test to fail. I'll work on fixing that but it looks like the Blazor tests are something different. Here's a reformatted version of one of the errors: Expected:
Actual:
|
@javiercn you mentioned you've been working on this PR while on build ops❔ Are you still on point❔ (I ask because Blazor issues aren't in my wheelhouse.) |
…108.4 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions From Version 7.0.0-beta.22464.4 -> To Version 7.0.0-beta.22558.4
I created #29009 to fix the regression in TargetPlatformVersion normalization. |
Looks like the Blazor failures for this PR are fixed by updating to the final 7.0.100 SDK. There's a mismatch somewhere in how the Blazor tests get the |
Depending on whether we're using preview versions, some of the packages may be downloaded by NuGet and have lowercased names, while at other times they may be shipped in the packs folder and have mixed case.
This pull request updates the following dependencies
From https://github.com/dotnet/arcade